3 ms·
I still like Linq2Sql better than EF. It always made more sense to me to have a sanely-designed database first and then generate the mapping code from it, rath
by thrower123 5y ago
I still like Linq2Sql better than EF.
It always made more sense to me to have a sanely-designed database first and then generate the mapping code from it, rather than the code-first style that seems to be popular with EF. You can do the database-first mode with entity framework, but it is less the happy path that the tooling and documentation tries to nudge you into.
- Weebs 5y agoI've always been frustrated that active record ORMs have completely overtaken tools like Linq2Sql. I don't deny the value of the active record pattern where it works, but in almost every case I've used SQL over the past 5 years, I don't want a complex abstraction layer. I just want something to make it easy and safe to talk to the database for the 90% of straight forward queries we write. With something like that, I feel as though I'd rather write my own active record system than use the configuration based systems we see with EF