Libary Settings Editor History Database Trigger and Function Missing from Upgraded Schemas

Bug #1450561 reported by Jason Stephenson
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Evergreen
Fix Released
Medium
Unassigned
2.7
Fix Released
Medium
Unassigned
2.8
Fix Released
Medium
Unassigned

Bug Description

The 002.schema.config.sql file creates a database function, limit_oustl, and a trigger, limit_logs_oust, on config.org_unit_setting_type_log that do not appear in an upgraded database. Their absence likely stems from the fact that they are missing from 0623.schema.YAOUS-log-table.sql, the upgrade script that creates the table upon which the trigger and function operate.

Furthermore, the limit_oustl function appears to have a bug in that it does not take org. unit into account when limiting the number of history entries kept. It keeps only the five latest settings on a global basis and not the latest five for each org. unit. It should actually take the org. unit from the NEW row into account when determining what rows to delete and/or keep.

Revision history for this message
Jason Stephenson (jstephenson) wrote :

Branch pushed to working repo at user/dyrcona/lp1450561-restore-coustl-limit-function-and-trigger

http://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/dyrcona/lp1450561-restore-coustl-limit-function-and-trigger

tags: added: pullrequest
Changed in evergreen:
milestone: none → 2.next
Changed in evergreen:
milestone: 2.next → 2.9-alpha
status: New → Triaged
importance: Undecided → Medium
Changed in evergreen:
milestone: 2.9-alpha → 2.9-beta
Revision history for this message
Ben Shum (bshum) wrote :

Seems logical to me. Pushed to master and backported to rel_2_8 and rel_2_7. One minor change in filename, I fixed a typo from lmit to limit in the name of the SQL upgrade script.

Changed in evergreen:
status: Triaged → 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.