3 ms·
The developers have constrained themselves by refusing anything that falls outside of the scope of a strongly typed unit-of-work implementation. This means we
by grouseway 5y ago
The developers have constrained themselves by refusing anything that falls outside of the scope of a strongly typed unit-of-work implementation.
This means we will probably never get:
1. Ability to pull non entity types out of the database without a whole lot of boilerplate. See the bizarre obstinacy here: https://github.com/dotnet/efcore/issues/10753 https://github.com/dotnet/efcore/issues/10753
2. Any kind of bulk insert/delete/update ability. It's been a "to do" for years now.
3. Much better query composability.
Basically their response is to just use raw SQL for anything that isn't a unit-of-work feature. They're missing a lot of benefits that a ORM could provide when they say that.
The ef.core team feels like a lot of rejects that were stack ranked out to their own team. I know that is mean to say, but they iterate extremely slowly compared to teams like asp.net .core, visual studio code, c# language group, f# language group.