3 ms·
who would rather spend more time maintaining/debugging/optimizing ORM code But that's kind of the point- with a decent ORM library there isn't really much work
by untog 14y ago
who would rather spend more time maintaining/debugging/optimizing ORM code
But that's kind of the point- with a decent ORM library there isn't really much work to do.
model = MyModel.load(id)
Add a new field to your model? It'll handle it. It might even modify the table for you. With raw SQL you'd have to go and edit your UPDATE and INSERT statements each time. Seems like a lot more maintenance/potential debugging to me.
- silverbax88 14y agoOkay, add a messaging trigger on update and insert between two joined permission tables, without creating a mutating trigger. SQL is about a lot more than CRUD and tables.
- zzzeek 14y agoso add a trigger to your tables. How is an ORM getting in the way of that?
- untog 14y agoSQL is rarely about a lot more than CRUD and tables. I would think that over 95% of the SQL code ever written has been CRUD operations. ORMs exist to simplify CRUD operations. If you are trying to do something that is a not a CRUD operation then you'd be mad to try and use an ORM to do it.