2 ms·
> WTF do I need an ORM for, if I understand enough to write an SQL command, and use a library for that DB that does parameterized queries? I am getting into fr
by cirgue 8y ago
> WTF do I need an ORM for, if I understand enough to write an SQL command, and use a library for that DB that does parameterized queries?
I am getting into frontend for a hobby project after spending a few years doing ML and applied stats, and I am currently asking myself this question. If your db interaction is simple, a query is almost as easy to write and maintain as an interaction with an ORM, and is significantly more flexible. If it is something more sophisticated, then your ORM quickly becomes more of a hindrance than a help. What am I missing here? Where is the virtue of an ORM beyond not having to use SQL?
- tracker1 8y agoIn more static languages, you generally need to convert from the DB types to the Native types to your language. This means a lot of code (more than boilerplate ORMs) and prone to a lot of mistakes. Some tooling that generates it for you helps a lot in some cases. I can see the appeal, but not in a dynamic language environment where there is less disconnect.