4 ms·
I think the correct approach is to understand the SQL that your ORM is using. If you can't have it create the correct query than roll your own. I think most of
by wuliwong 3y ago
I think the correct approach is to understand the SQL that your ORM is using. If you can't have it create the correct query than roll your own. I think most of the trouble people get in with ORMs is not taking the time to understand the SQL that it creates and using it incorrectly as a result.
- gigatexal 3y agoImo software engineers look to the ORM to abstract the declarative set-theory, blah blah of SQL back into the object model they’re familiar with. IMO that’s a dereliction of duty as a developer but it happens and ORMs have gotten pretty good of late. In the Java space the JOOQ team is doing really good work. In my space of Python SQLalchemy has been the dominate ORM of choice and I hated it but without putting out a better product I have just decided to work around it or adapt. But if I can I use raw SQL where possible.
- cqqxo4zV46cp 3y agoDjango’s ORM is also widely popular in the Python world. It’s just not standalone.