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 https://product-definition-center.github.io/product-definition-center/_image...
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 list.
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 happened?
Thanks!