EF Core Raw SQL Queries Make Dapper Unnecessary #shorts

preview_player
Показать описание

Рекомендации по теме
Комментарии
Автор

You need to add this to your course 😅 This is priceless!

mr.nobody
Автор

Some benchmark test need for check differences in perfomance between EF and Dapper

rasimismatulin
Автор

Very good improvement. Does exist something for more complex mappings like splitOn from dapper?

sergiom.
Автор

I'm new to EF and was very surprised this week about that not being supported. Even our in-house (weird) micro-orm had it.
Now I'm learning it's finally coming. Well, better late than never. I can keep learning EF then lol

junior.santana
Автор

DAPPER did school for actual libraries. I'm sure EF CORE doesn't have other features present in dapper.

micheleagnello
Автор

not necessarily need to check performance still.

kumailn
Автор

Finally a new feature that increases ef core read operations..

Hallo
Автор

Ahhh dapper in the mud here especially if performance is good

umarzakari
Автор

Can you execute stored procedures with this method?

amodavislava
Автор

if EF maps faster then Dapper, why not?

harunmn
Автор

I do not know how do you feel about it guys, but as C# develops it does not make me any sense. Like, first there were NHibernate, then it was copied and named EF, now copy Dapper. Same with Minimal Api and Carter, and so on. We talk about code reuse, but actually in dotnet we do not reuse anything, we just keep re-implementing things. I just feel it crazy. Why dont we just use the existing good stuff, why all good stuff needs to be re-implemented by microsoft and learned twice?

zbaktube