.NET Data Community Standup - EF Core internals: IQueryable, LINQ and the EF Core query pipeline
Vložit
- čas přidán 7. 03. 2023
- In this standup, we'll dive deep under the hood to see how EF Core processes LINQ queries, translates them to SQL and executes them on your database. We'll introduce key concepts such as IQueryable and LINQ providers, and see how EF Core uses caching to make your querying lightning-fast. Join us to understand how the magic works!
Featuring: Arthur Vickers (@ajcvickers), Shay Rojansky (@shayrojansky)
#EntityFramework #Beginner #CSharp - Věda a technologie
Yes, please make a follow up and dig deeper into those two compilation-boxes!
As shay outlines , Index based in memory datawell using LINQ and DI service is what we use to maintain State on WASM across pages to overcome cascading values issues e.g An Invoice which consists of 20 entities (nested interfaces) and with entity splitting.
Starts at 2:36
Thnx
thank you for the video.
In our company we have a legacy system that was created even before EF. Now I added a feature that allows linq for filtering which transforms the linq predicate expression into the filter that our legacy system recognizes. But that legacy system must at a certain point create SQL too, and materialize too, but then to our own classes. It does have change tracking, but does not have the notion of a context, that is hidden to the users, nor does it have a unit of work. But I was thinking that instead of writing my own visitor to create our legacy filters, i could get the SQL from the provider by perhaps adding some attributes or fluent api and fake context objects in our code. Ideally without changing any code in the provider. Because then with an update of the provider, I don't have the problem of code merging. But even if I have to dig through the provider code and use a subset of it, it would still be cool, because the quality of the sql generation is very likely very good.
In all honesty, you need proper guidance videos similar to this one in the documentation section on how internals work when a new version of EF is released.
we can say the expression is a func that is written in a single line of code without surrounding it with curly braces
and it has a #beginner tag :))
Is it not beginner friendly ?
That's a valid point @MohammadElmi. You need to be maybe an intermediate developer and have at least some experience programming EF Core by using a DbSet class to understand this video. It's about internals of EF Core and not an introduction to the topic.
the intro music is starts to be a bit repetitive