Trigger function maintaining hold-target mapping not well constrained

Bug #1657237 reported by Mike Rylander on 2017-01-17
26
This bug affects 4 people
Affects Status Importance Assigned to Milestone
Evergreen
Critical
Unassigned

Bug Description

Several sites simultaneously ran into an issue where the trigger function maintaining a materialized view of hold-target mappings was not properly constrained. The fix for this is coming now, and should immediately be applied to any 2.11 database that has not modified the infrastructure surrounding reporter.hold_request_record.

Galen Charlton (gmc) on 2017-01-17
Changed in evergreen:
assignee: nobody → Galen Charlton (gmc)
Galen Charlton (gmc) wrote :
Changed in evergreen:
assignee: Galen Charlton (gmc) → nobody
Bill Erickson (berick) on 2017-01-17
Changed in evergreen:
assignee: nobody → Bill Erickson (berick)
Bill Erickson (berick) wrote :

Tested and merged to master + rel_2_11.

Changed in evergreen:
status: Confirmed → Fix Committed
assignee: Bill Erickson (berick) → nobody
Mike Rylander (mrylander) wrote :

Here you'll find a branch that updates the upgrade script Bill stamped and merged above. The new change is important to apply at the same time as the trigger fix, as there is very likely incorrect data in the materialized view.

http://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/miker/lp-1657237-rhrr-cleanup

Changed in evergreen:
status: Fix Committed → Incomplete
status: Incomplete → Confirmed
Mike Rylander (mrylander) wrote :

Thanks, Jason. Merged to master and 2.11 for great justice.

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

Duplicates of this bug

Other bug subscribers