4 ms·
If Django replaced their very limited ORM for SQLAlchemy, I'd agree. There are just so many apps that end up requiring queries complex enough that with the Dja
by lucian1900 11y ago
If Django replaced their very limited ORM for SQLAlchemy, I'd agree.
There are just so many apps that end up requiring queries complex enough that with the Django ORM you have to resort to raw SQL. With SQLAlchemy, you can express any SQL you want without giving up composition.
- johnmaguire2013 11y agoWhy not just use SQLAlchemy with Django and ignore the built-in ORM?
- collyw 11y agoBecause the Admin and other features won't work?
- true_religion 11y agoIn order to get the admin and other features, all you need to do is define your models in Django's system. After that you can use SqlAlechemy as a side channel, just like a lot of people use NoSQL databases.
- ivoras 11y agoCan you give an example for a thing where with the Django ORM you have to resort to raw SQL?
- collyw 11y agoConditional aggregates were a problem until 1.8 or 1.9. Joins on more that one field would be another.
- lucian1900 11y agoArbitrary explicit joins make a lot of data reporting much easier.