Reporter hold request record table inconsistent aged holds handling
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Evergreen |
New
|
Undecided
|
Unassigned |
Bug Description
Evergreen 3.0+
As of version 2.11 reporter.
Arguably, retaining the data for purged holds may be useful for reporting. However, when the table was created in 2.11 it only included data from action.
Either the rows should disappear when a hold is deleted (via purging) or the table should be back-filled with aged holds data for consistency.
Given the original VIEW only cared about active hold requests, deleting the reporter.
Something along the lines of:
DELETE FROM reporter.
WHERE id IN (/* holds not in ahr */)
ALTER TABLE reporter.
ADD CONSTRAINT ahrfk FOREIGN KEY (id)
REFERENCES action.hold_request (id) ON DELETE CASCADE;
description: | updated |
PaILS learned from Equinox that this bug may be effecting the display of some volume level holds.
The holds still fill, they just don't display.