[Pulp-dev] Repo version implementation
daviddavis at redhat.com
Tue Dec 12 01:26:39 UTC 2017
That’s correct except for one small detail: version_added and
version_removed are two fields on a single model called
RepositoryContent. So it’s really two records total and not four.
It kind of brings up another point: when you remove a version where content
was removed but then re-added later, you end up with two RepositoryContent
records pointing to the same version. It’s an odd result but not only minor
in terms of severity. We should look at perhaps fixing it though if we
adopt proposal #2.
 https://git.io/vbExy (note that they’re called vadded and vremoved in
On Mon, Dec 11, 2017 at 5:18 PM, Jeremy Audet <jaudet at redhat.com> wrote:
> Regarding the second option: What happens if I (as a user) add a content
> unit to a repo, later remove it, later add it again, and later remove it
> again? Would this result in two "version_added" and two "version_removed"
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Pulp-dev