News for hackers. Stuff that matters.

A comment on Migrating to SQLAlchemy 2.0. Parent comment

Re:Migrating to SQLAlchemy 2.0 by darkhorse13 on Friday February 19, 2021 @08:12AM (#26192743)
>But I can’t imagine using an ORM for complex data tables and relationships with normalized data.

Whenever I read a statement like this from someone, I always feel that they actually haven't thoroughly read the docs for Django's ORM. Can you give me one concrete complex example that you can't imagine doing with the ORM? Because 95% of the time, these "complex" models are trivially easy to pull off with the ORM (from my experience).

[ Parent | on HN ]
Re:Migrating to SQLAlchemy 2.0 by ddorian43 on Friday February 19, 2021 @09:19AM (#26193388)
Django orm doesn't support composite primary keys.
[ Parent | on HN ]
Re:Migrating to SQLAlchemy 2.0 by BiteCode_dev on Friday February 19, 2021 @10:46AM (#26194332)
The beauty of the Django ecosystem, is that you have packages for everything: djangopackages.org

E.G: https://github.com/Arisophy/django-compositepk-model

[ Parent | on HN ]
Re:Migrating to SQLAlchemy 2.0 by darkhorse13 on Friday February 19, 2021 @10:45AM (#26194324)
Fair enough. There is `unique_together` though, which you may look into.
[ Parent | on HN ]