✅ EF Core "Disconnected" Architecture Vs Ado.NET
Hello guys, can someone explain how EF core works under the hood please. I read that it just loads data in memory, everything is done in memory and all changes are made to the database when we use method like
But it may happen we don't need that method either like when we use the
I would really appreciate if someone can clarify how both the EF Core and ADO.Net architecture works :C
SaveChanges(). But it may happen we don't need that method either like when we use the
ExecuteDelete or ExecuteUpdate (I think, don't know how this works though). I was wondering how is this different from ADO.Net; in ADO.Net we have a choice of connected and disconnected architecture? Like I know we can use DbSet I think to load entire entity in it, then work from that.I would really appreciate if someone can clarify how both the EF Core and ADO.Net architecture works :C
