Project

Profile

Help

Task #7195

closed

Enforce correct uniqueness for UpdateCollection at the Model level

Added by ggainey over 2 years ago. Updated over 2 years ago.

Status:
CLOSED - CURRENTRELEASE
Priority:
High
Assignee:
Sprint/Milestone:
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

Related to RPM Support - Issue #6815: Not all advisory models are defined for import/exportCLOSED - CURRENTRELEASEggaineyActions

Also available in: Atom PDF