2 ms·
Some people, when faced with a database problem, choose to use an ORM on top of an RDBMS. Those people now have three problems. The problems are: the original
by cryptonector 9y ago
Some people, when faced with a database problem, choose to use an ORM on top of an RDBMS. Those people now have three problems.
The problems are: the original problem, the expressive and performance disaster that is every ORM ever, and the layered and hidden RDBMS whose peculiarities nonetheless always find a way to leak through the ORM abstraction.
Fun stuff.
Do what TFA says: just learn SQL.
- Demiurge 9y agoI've been using Django + Django ORM for a decade, and it has covered vast majority of database usage. Entire applications written with zero SQL, and clean DRY code describing data and allowing to use it in the code. And yet other application written with lots of SQL. The real question is, why anyone using an ORM not learning SQL, how the the thing they are mapping to objects actually works?