Django ORM Critique

Discussions center on the strengths, weaknesses, and limitations of Django's ORM, including data modeling, relationships, migrations, and comparisons to alternatives like SQLAlchemy.

📉 Falling 0.3x Databases
1,427
Comments
19
Years Active
5
Top Authors
#9998
Topic ID

Activity Over Time

2008
20
2009
34
2010
67
2011
48
2012
124
2013
109
2014
76
2015
45
2016
55
2017
93
2018
60
2019
62
2020
84
2021
104
2022
82
2023
204
2024
85
2025
74
2026
1

Keywords

EAV SQL djangoproject.com OK article.id models.py bitbucket.org OOP ORM manage.py django orm models model database sqlalchemy object unexpected relationships logic

Sample Comments

tedmiston Jul 5, 2017 View on HN

Not sure what you mean by this. You have full control over your table schemas and relationships with the Django ORM.

eyelidlessness Feb 5, 2021 View on HN

Django is just plain bad at data modeling there I said it

eru Nov 9, 2022 View on HN

Well, Django has an ORM that makes this kind of feature necessary in the first place? ORM's are trying to hide the relational nature of your db, don't they?

edraferi May 27, 2020 View on HN

Can you provide a more detailed critique of Django’s “Fat Models” recommendation? How would you prefer to manage this logic?

stefano Apr 7, 2019 View on HN

Don't the Django ORM and Django Admin do the same thing?

aneesh Jun 19, 2009 View on HN

Have they added support for Django models as well?

BarryMilo Sep 1, 2024 View on HN

Aren't Django models close enough to types?

baddox Aug 22, 2010 View on HN

That's interesting how they made it jive with Django's ORM.

mixedbit Jun 16, 2013 View on HN

Why Django model is not an ORM?

creshal Mar 27, 2023 View on HN

This is not a Python problem, it's a design decision of Django's ORM specifically.