2 ms·
Why is it one vs other? It's not, you can run them both. The question is why you would. What does an ORM solve for you? This is the only mapping I need from an
by lugg 8y ago
Why is it one vs other? It's not, you can run them both. The question is why you would. What does an ORM solve for you?
This is the only mapping I need from an ORM:
result = (object) row
row = (array) result
SQL does everything an ORM does better.
I'm not sure how you can call moving from a low level programming language to a domain specific language like SQL "going lower". It's not and ORMs are usually so bad they're a regression in what you can do.
Also, when was the last time a change to the SQL spec broke your app?what about the last times you had to migrate ORM code?
- ken 8y ago> Also, when was the last time a change to the SQL spec broke your app?what about the last times you had to migrate ORM code? That's kind of an arbitrary categorization. An ORM is just a library. If you asked me when the last time I had to update my code because a library changed interfaces, I'd have an answer for you (less than a month ago, I'm sure). I'm not going to stop using libraries, though. I've had to update my programs several times because my compiler was updated, too. That may make me choosier in the future about which compiler I pick, but I'm not going to stop using compilers altogether.