Missing db functions in 3.0.1-3.0.2 upgrade script
Bug #1772028 reported by
Bill Ott
This bug affects 3 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Evergreen |
Fix Released
|
High
|
Unassigned | ||
3.0 |
Won't Fix
|
High
|
Unassigned | ||
3.1 |
Fix Released
|
High
|
Unassigned | ||
3.2 |
Fix Released
|
High
|
Unassigned |
Bug Description
While working through upgrade scripts, I found several functions missing from my database. I don't see them added in another script, so it should be benign to just do a CREATE OR REPLACE before adding triggers for them.
Changed in evergreen: | |
status: | New → Confirmed |
importance: | Undecided → High |
milestone: | none → 3.2-beta |
Changed in evergreen: | |
milestone: | 3.2-beta → 3.1.3 |
no longer affects: | evergreen/3.1 |
Changed in evergreen: | |
milestone: | 3.1.3 → 3.1.4 |
Changed in evergreen: | |
milestone: | 3.1.4 → 3.1.5 |
Changed in evergreen: | |
milestone: | 3.1.5 → 3.1.6 |
Changed in evergreen: | |
milestone: | 3.1.6 → 3.2.1 |
Changed in evergreen: | |
milestone: | 3.2.1 → 3.2.2 |
Changed in evergreen: | |
milestone: | 3.2.2 → 3.2.3 |
Changed in evergreen: | |
milestone: | 3.2.3 → 3.3-beta1 |
Changed in evergreen: | |
milestone: | 3.3-beta1 → 3.3-rc |
Changed in evergreen: | |
milestone: | 3.3-rc → 3.3.1 |
Changed in evergreen: | |
milestone: | 3.3.1 → 3.3.2 |
Changed in evergreen: | |
assignee: | nobody → Dan Wells (dbw2) |
Changed in evergreen: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
I set this to confirmed and high because I see the functions are missing from any upgrade scripts. That said, I seem to have all but the last one, evergreen. asset_copy_ alert_copy_ inh_fkey, in a database that was upgraded from 2.12.8 to 3.0.7 using the upgrade scripts. I don't know where the functions came from unless they were always there or were added to our production database at some point prior to the dump and test upgrade. I don't remember adding them, myself.
Also I am not sure that editing a published upgrade script is the best way to go. We may want to do that and create a new upgrade script for those who won't re-run the 3.0.1-3.0.2 upgrade.