Why should you care?

ShopNest admins edit prices, stock, and order status — updates must touch only changed columns safely.

See it live — copy this example

Paste into a .NET project with EF Core packages, then run with LocalDB/SQL Server (dotnet ef / dotnet run).

var product = await _context.Products.FindAsync(id);
if (product is null) return NotFound();

product.Price = newPrice;
product.StockQty = newStock;
await _context.SaveChangesAsync();
// UPDATE sets only modified columns when tracked

What happened?

• FindAsync tracks the entity.
• Property assignments mark fields Modified.
• SaveChangesAsync emits UPDATE with changed columns only.

Practice next

1. Load, change Price, save, and compare SQL log to full-row UPDATE.
2. Try Update() on detached entity — marks all properties Modified.
3. Use entry.Property().IsModified for selective updates on attached entities.
4. Use ExecuteUpdateAsync in bulk lesson contrast — here stay with tracked single row.
5. Attach stub Product { Id = 5, Price = 10 } and set Entry.State Modified selectively.

Remember

Tracked mutations generate targeted UPDATEs. Update() marks whole entity Modified — use carefully. Patch APIs should load then change specific fields.

ShopNest flash price change

Pricing admin updates Product.Price and StockQty on tracked entity during sale event.

Outcome: Minimal column UPDATE reduces lock duration on hot rows.