Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »

Welcome to Software Development on Codidact!

Will you help us build our independent community of developers helping developers? We're small and trying to grow. We welcome questions about all aspects of software development, from design to code to QA and more. Got questions? Got answers? Got code you'd like someone to review? Please join us.

Review Suggested Edit

You can't approve or reject suggested edits because you haven't yet earned the Edit Posts ability.

Approved.
This suggested edit was approved and applied to the post over 1 year ago by Alexei‭.

49 / 255
  • What you want would be called `DbSet<>.Find()` combined with eager loading of the related entities. According to [the docs](https://learn.microsoft.com/en-us/dotnet/api/microsoft.entityframeworkcore.dbset-1.find?view=efcore-7.0), eager loading is not mentioned and its sole purpose is to easily get an entity based on its type and keys:
  • > Finds an entity with the given primary key values. If an entity with the given primary key values is being tracked by the context, then it is returned immediately without making a request to the database. Otherwise, a query is made to the database for an entity with the given primary key values and this entity, if found, is attached to the context and returned. If no entity is found, then null is returned.
  • In order to get an entity and its related entities, you can rely on a LINQ filter function + Include:
  • ```c#
  • var blog = db.Blogs
  • .Include(b => b.Posts)
  • .FirstOrDefault(b => b.Id == id);
  • ```
  • This will generate a query to fetch data for both the blog with and its associated posts (eager loading of the posts).
  • Note: For scenarios where performance is important, you can only fetch the required columns. Example:
  • ```c#
  • var blogInfo = db.Blogs
  • .Select(b => new
  • {
  • BlogId = b.BlogId, // explicit property name
  • BlogUrl = b.Url,
  • PostData = b.Posts.Select(p => new { p.Id, p.Title })
  • }
  • .FirstOrDefault(b => b.BlogId == id);
  • ```
  • Of course, a DTO can be used instead of anonymous types. The interesting part is that EF Core (5+) figures out automatically that Posts columns are required and no explicit `Include()` is required.
  • What you want would be called `DbSet<>.Find()` combined with eager loading of the related entities. According to [the docs](https://learn.microsoft.com/en-us/dotnet/api/microsoft.entityframeworkcore.dbset-1.find?view=efcore-7.0), eager loading is not mentioned and its sole purpose is to easily get an entity based on its type and keys:
  • > Finds an entity with the given primary key values. If an entity with the given primary key values is being tracked by the context, then it is returned immediately without making a request to the database. Otherwise, a query is made to the database for an entity with the given primary key values and this entity, if found, is attached to the context and returned. If no entity is found, then null is returned.
  • In order to get an entity and its related entities, you can rely on a LINQ filter function + Include:
  • ```cs
  • var blog = db.Blogs
  • .Include(b => b.Posts)
  • .FirstOrDefault(b => b.Id == id);
  • ```
  • This will generate a query to fetch data for both the blog with and its associated posts (eager loading of the posts).
  • Note: For scenarios where performance is important, you can only fetch the required columns. Example:
  • ```cs
  • var blogInfo = db.Blogs
  • .Select(b => new
  • {
  • BlogId = b.BlogId, // explicit property name
  • BlogUrl = b.Url,
  • PostData = b.Posts.Select(p => new { p.Id, p.Title })
  • }
  • .FirstOrDefault(b => b.BlogId == id);
  • ```
  • Of course, a DTO can be used instead of anonymous types. The interesting part is that EF Core (5+) figures out automatically that Posts columns are required and no explicit `Include()` is required.

Suggested over 1 year ago by Sylvester‭