3 ms·
ORMs are great for simple CRUD operations. As soon as you want to do anything mildly complex or desire efficiency, you need to write SQL. As long as the ORM he
by meritt 12y ago
ORMs are great for simple CRUD operations. As soon as you want to do anything mildly complex or desire efficiency, you need to write SQL.
As long as the ORM helps me with the former and gets out of my way for the latter, I'm totally happy to utilize then.
- silverbax88 12y agoI agree with this, but SQL is also great for writing CRUD, and 99% of database interaction is CRUD.
- spacemanmatt 12y agoThat may be true by frequency of query execution, but not by frequency of appearance in an application.
- aikah 12y agothat's absolutely not true.Sure you cant write a procedure with an ORM. But good ORM have query builders that with allow you not to write ANY sql.At all.ORMs are not just about CRUD at all.
- GrinningFool 12y agoThe biggest downside to this that I found is that you have to have a lot of trust in the creators of that ORM. SUre, it will generate a query that gets you what you want - but will it use the right indices? Will use correct ordering for optimal results? Generally (unless this has changed in more recent years) the answer is 'no'.
- deleted 12y ago[deleted]