3 ms·
Type safe sql is a feature of most every production quality db library I’ve used going back 20 years. You don’t need the complexity of an orm to get that. As f
by kasey_junk 3y ago
Type safe sql is a feature of most every production quality db library I’ve used going back 20 years. You don’t need the complexity of an orm to get that.
As for trivial boilerplate, I tend to find that trivial boilerplate no more troubling than any of the other compromises orms require, whether that’s polluting my data model with sql concerns or making me conform to db practices that aren’t correct for my needs.
And I’ve got extensive experience with orm going back a long time, including Entity Framework (which is a good orm that I’d still prefer not to use).
- tptacek 3y agoI still find myself having the experience of having to unit test trivialities with direct SQL coding, lest I miss a typo, which is a (very basic) thing any ORM or query wrapper will tend to save me from.
- kasey_junk 3y agoI need to do the same thing with attributes, naming conventions, etc that are typically required to make orms work.