[Pulp-list] Pulp 3.0 Technology Stack Justifications

[Mihai Ibanescu]

My personal experience with django as an ORM is less than stellar, but that
was based on an older version of django that I had to retrofit on existing
schema. For instance, the ORM insists that every table has to have an 'id'
primary key, even many-to-many tables. While not incorrect, it's annoying
and unnecessary in my opinion - the primary key would be a composite of the
two foreign keys. Maybe it's easier if you start with a clean schema. I
like sqlalchemy much better, personally.

Maybe the orm has changed recently.

Mihai's $0.02

On Tue, May 17, 2016 at 1:55 PM, Sean Myers <sean.myers at redhat.com> wrote:

> Based on the feedback so far, I haven't seen any issues with what
> I've proposed here other than elasticsearch. I'll be digging into
> that piece of the stack and revaluating the options out there,
> taking the feedback from this thread into account.
>
> Thanks!
>
>
> _______________________________________________
> Pulp-list mailing list
> Pulp-list at redhat.com
> https://www.redhat.com/mailman/listinfo/pulp-list
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/pulp-list/attachments/20160517/8aac1014/attachment.htm>