Libary Settings Editor History Database Trigger and Function Missing from Upgraded Schemas
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.
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.
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 |
Changed in evergreen: | |
status: | Fix Committed → Fix Released |
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