3 ms·
People who avoid ORMs endup writing their own worse ORM*. ORMs are perfect if you know how and when to uses them. They encapsulate a lot of the mind numbing wo
by kaptainscarlet 1y ago
People who avoid ORMs endup writing their own worse ORM*. ORMs are perfect if you know how and when to uses them. They encapsulate a lot of the mind numbing work that comes with raw sql such as writing inserts for a 50 column database.
- djdjnm 1y agoI did that once on a hobby project, accidentally. When I realized the corner I had painted myself into I abandoned it.
- itake 1y ago100%. I once tried to optimize a SQL query, moving away from the ORM, so I can have more control of the query structure and performance. I poorly implemented SOLID design principles, creating a complete mess of a SQL Factory, which made it impossible to reason about the query unless I had a debugger running and called the API directly.
- adampwells 1y agoI find that Claude writes boilerplate SQL very well, and is effectively an 'ORM' for me - I just get plain SQL for CRUD. Complex queries I write myself anyway, so Claude fills the 'ORM' gap for me, leaving an easily understood project.
- Too 1y agoWriting is just half the job. Now try migrations, or even something as fundamental as ”find references” on a column name. No, grep is not sufficient, most tables have fields called ”id” or ”name”.