4 ms·
I'd add #4 - it's just generally faster and more enjoyable to develop with a good ORM.
by exclusiv 9y ago
I'd add #4 - it's just generally faster and more enjoyable to develop with a good ORM.
- andybak 9y agoYep. Learned SQL. Happy never to have to touch it again.
- randomdata 9y agoAlthough, I think what you plan to do with the data also makes a big difference. Which probably explains why opinions vary so widely. For short-lived processes, like typical web applications and command line utilities – that load data from the database, do something with it, and then purge it from memory again – I'm becoming less and less convinced that ORMs are actually a benefit. On the other hand, if your application plans to map the database data to memory for long periods of time, with the need to keep them in sync, then you're probably going to end up writing something that resembles an ORM anyway, and poorly at that. In this case a good ORM is beneficial.