2 ms·
I'm in the camp of liking SQLAlchemy, and not really liking Django's ORM, which I am admittedly much less familiar with. I especially find Django's functionalit
by vosper 9y ago
I'm in the camp of liking SQLAlchemy, and not really liking Django's ORM, which I am admittedly much less familiar with. I especially find Django's functionality for aggregations to be completely arcane and a long way from the SQL that I am modeling in my head. I wonder if that's what it comes down to - as someone who tends to think in terms of the SQL I want to build I find SQLAlchemy to be a lot closer to my mental model than Django.
For just getting an object by ID I don't think there's much difference, for me.
I think one thing in Django's favour is that SQLAlchemy can be confusing to setup (do I need scoped sessions?). Also, you need to find and setup your own solution for migrations, whereas Django will just sort that out for you. So getting up and running is a lot easier.
- phonon 9y ago> I especially find Django's functionality for aggregations to be completely arcane and a long way from the SQL that I am modeling in my head. Do you mean https://docs.djangoproject.com/en/dev/topics/db/aggregation/ https://docs.djangoproject.com/en/dev/topics/db/aggregation/ and https://docs.djangoproject.com/en/dev/ref/contrib/postgres/aggregates/ https://docs.djangoproject.com/en/dev/ref/contrib/postgres/a... ? How would you improve it?