3 ms·
Honestly the main reason I still use an ORM right now (Gorm, it's not the best), is to solve a number of annoyances I would otherwise have (and I may yet switch
by Cthulhu_ 6y ago
Honestly the main reason I still use an ORM right now (Gorm, it's not the best), is to solve a number of annoyances I would otherwise have (and I may yet switch to straight SQL): mapping result sets to structs, updating relationships (treating nested objects as a single document), and database migrations.
I really don't mind SQL, I mind all the perceived boilerplate around it.
- marvinblum 6y agoThere is sqlx for that: https://github.com/jmoiron/sqlx https://github.com/jmoiron/sqlx
- geophile 6y agoYes, exactly. When I write SQL applications now, I usually start by implementing a little database interface to take care of the boilerplate. The application can then provide SQL as needed.