updates to monolithic schema update script for 3.0-rc

Bug #1719726 reported by Galen Charlton
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Evergreen
Fix Released
Medium
Unassigned

Bug Description

This is a bug for final tweaks to the schema update script for 2.12.x to 3.0-rc, including:

- incorporating 1077
- speeding up update of bib visibility cache
- authority reingeset

Evergreen master

Tags: pullrequest
Galen Charlton (gmc)
Changed in evergreen:
assignee: nobody → Galen Charlton (gmc)
Revision history for this message
Galen Charlton (gmc) wrote :

Patches are now available in the user/gmcharlt/lp1719726_3_0_rc_schema_update branch:

http://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/gmcharlt/lp1719726_3_0_rc_schema_update

tags: added: pullrequest
Galen Charlton (gmc)
Changed in evergreen:
assignee: Galen Charlton (gmc) → nobody
Revision history for this message
Galen Charlton (gmc) wrote :

I've updated the branch with some additional corrections to help ensure that a 2.12.5 database upgraded to 3.0 and a stock 3.0 database have essentially the same schema:

- ensuring that asset.copy_tag_copy_map.copy has a fake FK
- ensuring that the default value for config.metabib_field.display_field is consistent
- ensuring that two authority functions have the same code
- ensuring that the FK constrain on action.fieldset.fieldset_group is ON DELETE CASCADE

Revision history for this message
Mike Rylander (mrylander) wrote :

Re the first commit (1077), I think the baseline should be updated to create the triggers using the schema-qualified name of the function. Everything should just work, of course, but consistency is beneficial. That can probably wait for the time between RC and GA.

Re the third commit (authority reingest), I think we should leave the internal flag there, even if it didn't exist when the script walked up to the database.

Now, on to commits added since this morning!

Revision history for this message
Mike Rylander (mrylander) wrote :

Well, first, back to the second commit.

We'll want to disable the z_opac_vis_mat_view_tgr trigger on biblio.record_entry, along with the others. Pre-patch, the update that sets bre.vis_attr_vector was happening before that trigger was created, and we want to retain that behavior, I believe.

Revision history for this message
Mike Rylander (mrylander) wrote :

The rest of the commits look great. Thanks, Galen!

Branch coming soon with my above-suggested changes and signoffs.

Revision history for this message
Mike Rylander (mrylander) wrote :
Revision history for this message
Galen Charlton (gmc) wrote :

End result pushed to master. Thanks, Mike!

Changed in evergreen:
status: New → Fix Committed
Changed in evergreen:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.