Need more "IF EXISTS" clauses in 2.3-2.4.0-upgrade-db.sql
Bug #1205061 reported by
Robert Soulliere
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Evergreen |
Fix Released
|
Medium
|
Unassigned | ||
2.7 |
Fix Released
|
Undecided
|
Unassigned | ||
2.8 |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
EG Version: 2.3 - 2.4 upgrade
When upgrading from 2.3 to 2.4 the 2.3-2.4.
Could "IF EXISTS" clauses be added to these line and other DROP statements in order to alleviate this?
Here are some examples with line numbers where the script was "Rolling back" becuase of non-existent entities being dropped:
75 DROP INDEX metabib.
1928 DROP RULE protect_
2183 DROP CONSTRAINT z3950_attr_
Changed in evergreen: | |
milestone: | 2.5.1 → 2.5.2 |
Changed in evergreen: | |
milestone: | 2.5.2 → none |
Changed in evergreen: | |
milestone: | 2.8-beta → 2.8.1 |
Changed in evergreen: | |
milestone: | 2.8.1 → 2.9-alpha |
no longer affects: | evergreen/2.6 |
Changed in evergreen: | |
status: | Triaged → Fix Committed |
Changed in evergreen: | |
milestone: | 2.9-alpha → 2.9-beta |
Changed in evergreen: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
Marking potential series targets for 2.4 and 2.5.