User tests: Successful: Unsuccessful:
Add the parameter IF EXISTS
after DROP INDEX
.
Update Joomla! from version 3.9.15 or older.
No error.
The update with postgresql throws an error.
Status | New | ⇒ | Pending |
Category | ⇒ | Postgresql SQL Administration com_admin |
@twister65 Your PR looks right to me, and I've just checked that the database checker can handle the "IF EXISTS" for the index. But I can't reproduce the issue without your PR. Just updated a 3.9.15 to 3.9.18 using PostgreSQL 10, and I did not get any SQL error in the logfile or the UI. Can it depend on server settings if I get an error or not? Or does the problem only happen for certain versions, or installations with a certain update history?
I have tested this item
I couldn't reproduce the issue with updating a 3.9.15 to 3.9.18, but this may depend on the update history of a particular installation.
The change in this PR is correct and makes updating more safe, and I've verified that the database schema checker can handle "DROP INDEX IF EXISTS" for PostgreSQL.
For testing the update with this PR applied I've used the custom update URL for the update package built for this PR by drone.
I have tested this item
Status | Pending | ⇒ | Ready to Commit |
RTC
Status | Ready to Commit | ⇒ | Fixed in Code Base |
Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2020-05-03 08:14:52 |
Closed_By | ⇒ | HLeithner | |
Labels |
Added:
?
|
Thanks
Hint for testers: For testing this PR you can use the update package built for this PR by our checkin tools (Drone). You can find update packages and at the bottom a cutom update URL at following page: https://ci.joomla.org/artifacts/joomla/joomla-cms/staging/28902/downloads/31730/.