Tag feed

#entity-framework

125 posts69 followers

Explore Hashnode

Alternatives

Trending tags this week

Sspipaliya8sudhirpipaliya.hashnode.dev17h ago · 13 min read

EF Core Include vs Select: Which One Should You Use?

When working with Entity Framework Core, developers often use Include() to load related data. But there is another powerful approach: Select() So which one should you use? The answer depends on what

0

Sspipaliya8sudhirpipaliya.hashnode.devSep 7 · 12 min read

EF Core Query Splitting vs Single Query: Which One Should You Use?

Entity Framework Core makes it very easy to load related data using Include() and ThenInclude(). For example: var students = await context.Students .Include(x => x.Standard) .Include(x => x.Di

0

Sspipaliya8sudhirpipaliya.hashnode.devSep 2 · 9 min read

Why Database Indexes Matter for EF Core Performance

Entity Framework Core makes it easy to query data using LINQ. But even a well-written EF Core query can become slow when your database grows. One of the most important factors behind query performance

0

PKPatrick Kearnsfullstackcity.comSep 1 · 13 min read

When AsNoTracking Makes EF Core Slower

There is a piece of EF Core advice that appears in almost every performance discussion: If the query is read-only, use AsNoTracking(). Its usually good advice. Tracking entities requires EF Core to

1

R

CDCoding Dropletscodingdroplets.comAug 4 · 12 min read

Unable to Create an Object of Type DbContext in EF Core: Causes and Fixes

You add an entity, run dotnet ef migrations add AddOrders, and the tooling stops dead: Unable to create an object of type 'AppDbContext'. For the different patterns supported at design time, see https

0

EAEugene Atinbireayinenongre.hashnode.devJul 28 · 4 min read

How I Reduced Build Time from Over 5 Minutes to Under 30 Seconds by Consolidating 400+ Entity Framework Migrations

As developers, we often focus on optimizing application performance for our users, but we sometimes overlook something just as important our own developer experience. In our case, one of the biggest p

0

Qqodorsqodors.hashnode.devJul 25 · 5 min read

The N+1 Query Problem in EF Core (And How to Spot It Before Production Does)

A page that felt fine in testing is slow in production. Same code, same query, but now it crawls. You open the SQL log and there it is — not one query, but two hundred. One to load the list, then one

0

Qqodorsqodors.hashnode.devJul 22 · 6 min read

EF Core Is Already a Repository. Stop Wrapping It in Another One.

Open a lot of .NET projects and you'll find the repository pattern sitting on top of Entity Framework Core. IProductRepository, GetById, Add, Save, the whole set. Underneath, every method just calls t

0

Qqodorsqodors.hashnode.devJul 10 · 5 min read

AsNoTracking: The EF Core Setting Your Read Queries Are Missing

Most of the queries in a typical app are reads. You fetch data, show it, and never change it. EF Core doesn't know that. By default it assumes every entity you load might be modified and saved back, s

0

Qqodorsqodors.hashnode.devJul 9 · 6 min read

IQueryable vs IEnumerable: The Mistake That Loads Your Whole Table

You wrote a clean LINQ query. It filters down to ten rows. It runs fine in dev, and then in production it's slow and your database CPU is higher than it should be for such a small result. The query lo

0

#entity-framework

Search Hashnode

#entity-framework

Explore Hashnode

Trending tags this week

EF Core Include vs Select: Which One Should You Use?

EF Core Query Splitting vs Single Query: Which One Should You Use?

Why Database Indexes Matter for EF Core Performance

When AsNoTracking Makes EF Core Slower

Unable to Create an Object of Type DbContext in EF Core: Causes and Fixes

How I Reduced Build Time from Over 5 Minutes to Under 30 Seconds by Consolidating 400+ Entity Framework Migrations

The N+1 Query Problem in EF Core (And How to Spot It Before Production Does)

EF Core Is Already a Repository. Stop Wrapping It in Another One.

AsNoTracking: The EF Core Setting Your Read Queries Are Missing

IQueryable vs IEnumerable: The Mistake That Loads Your Whole Table