News for hackers. Stuff that matters.
Re:Django 2.1 released by djsumdog on Wednesday August 01, 2018 @01:04PM (#17664441)
I mean that's a general problem with ALL ORMs. I've been on Django projects where we had to drop down and pass raw SQL statements.

On my current project we don't use an ORM; just SQL statements and we create classes to match the result set and map into them.

Re:Django 2.1 released by blattimwind on Wednesday August 01, 2018 @01:29PM (#17664713)
Disagree. It's mostly a question of whether the ORM was designed as a "least-common denominator of common operations supported by some RDBMSs" (which is clearly the case for the Django ORM) or as an abstraction of SQL concepts (i.e. a form of relational algebra). The former category generally fares poorly with complex queries or structures; the latter exceeds at them.
Re:Django 2.1 released by Serow225 on Wednesday August 01, 2018 @01:32PM (#17664768)
What are some good examples of the latter type of ORM? Thanks
Re:Django 2.1 released by blattimwind on Wednesday August 01, 2018 @01:35PM (#17664807)
sqlalchemy