DB Doesn't protect against precat merges
Bug #827356 reported by
Mike Rylander
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Evergreen |
Fix Released
|
Medium
|
Unassigned | ||
3.6 |
Fix Released
|
Medium
|
Unassigned |
Bug Description
Following on from bug #792595, the UI now protects the magical precat bib (id=-1) from going into buckets, which is a primary entry point for being able to merge it. However, it's still possible to merge it in other ways (such as directly in the db, via the stored proc).
We should consider protecting all magic objects (bre.id=-1, acn.id=-1, acl.id=1, aou.id=1, au.id=1, etc) from merging, deletion, etc.
Changed in evergreen: | |
status: | New → Incomplete |
Changed in evergreen: | |
status: | Incomplete → Triaged |
Changed in evergreen: | |
assignee: | nobody → Rogan Hamby (rogan-hamby) |
Changed in evergreen: | |
assignee: | Rogan Hamby (rogan-hamby) → nobody |
tags: | added: bitesize |
Changed in evergreen: | |
assignee: | nobody → Rogan Hamby (rogan-hamby) |
Changed in evergreen: | |
milestone: | 3.6.4 → 3.7.2 |
tags: | added: precats |
Changed in evergreen: | |
assignee: | Rogan Hamby (rogan-hamby) → nobody |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
Similar, subsequent bug 1849334 - scoped to precat volume editing.