Re: PDC replacement proposal

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]


On Wed, 2023-09-13 at 16:49 +0200, Tomas Hrcka wrote:
> I thought this was exactly the JSON blob we will implement, If you look at
> the model of PDC
> Those endpoints are covered by relations Release, Compose, RPM through some
> others.
> The PDC approach is more or less a normalized RDBMS model.
> This should be replaceable by a much simpler denormalized approach and
> create one entry for each compose with all the data in one place.

That's missing the 'composes' endpoint use (#1 in my list below). Not
sure if that's your fault or mine, sorry if I left it out of a previous

Does your replacement plan cover the "previous_release" use case, where
we need a list of all the composes for each release in the order they

Adam Williamson (he/him/his)
Fedora QA
Fedora Chat: | Mastodon: @adamw@xxxxxxxxxxxxx

devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct:
List Guidelines:
List Archives:
Do not reply to spam, report it:

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Users]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]

  Powered by Linux