4 ms·
The idea that some library can abstract away database concerns to this extent is wishful thinking. You inevitably need to understand the SQL that your ORM is g
by djrobstep 6y ago
The idea that some library can abstract away database concerns to this extent is wishful thinking.
You inevitably need to understand the SQL that your ORM is generating and what the database is actually doing. Otherwise you're flying blind.
- airstrike 6y agoI never claim it replaces SQL entirely and that therefore users can "fly blind", as you put it. But the whole point of the ORM is to abstract away part of it
- TylerE 6y agoRealistically what ends up happening is that the DB gets abstracted away to a painfully feature-free lowest common denominator.
- bastawhiz 6y agoDjango handles this quite nicely. You get your basic lowest common denominator subset by default. If you want something more powerful, you can explicitly import a db-specific feature. And for some features, you'll get a NotImplemented exception. In the ten years I've been using Django, I've only seen these a handful of times, and only when using SQLite.