How to handle self-referencing tables (e.g. Employee has manager, manager is

Short answer: lso Employee)? Define navigation property and foreign key for self-reference. Use Fluent API: .HasOne(e => e.Manager).WithMany(e => e.Subordinates). lso Employee)? Define navigation property and foreign key for self-reference. Use Fluent API: .HasOne(e => e.Manager).WithMany(e => e.Subordinates). lso Employee)? Define navigation property and foreign key for… self-reference. Use Fluent API: .HasOne(e =>…

Explain a bit more

e.Manager).WithMany(e => e.Subordinates). lso Employee)? Define navigation property and foreign key for self-reference. Use Fluent API: .HasOne(e => e.Manager).WithMany(e => e.Subordinates).

Real-world example (ShopNest)

ShopNest’s order service uses EF Core to save an Order and its line items in one SaveChangesAsync() call inside a transaction.

Say this in the interview

1. Define — one clear sentence (the short answer above).
2. Example — relate it to a project like ShopNest or your real work.
3. Trade-off — when you would not use it.