Actions
Task #7195
closed
Enforce correct uniqueness for UpdateCollection at the Model level
Start date:
Due date:
% Done:
100%
Estimated time:
Platform Release:
Groomed:
No
Sprint Candidate:
No
Tags:
Sprint:
Sprint 79
Quarter:
Description
UpdateCollection needs to
a) be many-to-one FK linked to UpdateRecord, rather than ManyToMany, and b) be (name, update-record-id) unique
See https://pulp.plan.io/issues/6815#note-7 for details - this should be done as its own unit of work, rather than obscured by an issue that needs it to exist.
Related issues
Updated by ggainey over 4 years ago
- Related to Issue #6815: Not all advisory models are defined for import/export added
Updated by ggainey over 4 years ago
- Tracker changed from Issue to Task
- Status changed from NEW to ASSIGNED
- Assignee set to ggainey
- % Done set to 0
- Severity deleted (
2. Medium) - Triaged deleted (
No)
Updated by pulpbot over 4 years ago
- Status changed from ASSIGNED to POST
Added by ggainey over 4 years ago
Updated by ggainey over 4 years ago
- Status changed from POST to MODIFIED
- % Done changed from 0 to 100
Applied in changeset 6ded98fc80faabf8b83f06c509ad0c149b9794f9.
Updated by pulpbot over 4 years ago
- Status changed from MODIFIED to CLOSED - CURRENTRELEASE
Actions
.
Make UpdateCollection be unique by (name,update_record).
Migrate existing data and make UpdateCollection be 1to1 to UpdateRecord along the way.
fixes #7195 [nocoverage]