> Unfortunately basic mistakes can result in so many of those N+1 type queries if you're not careful. It can also result in reading entire table(s), possibly in

> Unfortunately basic mistakes can result in so many of those N+1 type queries if you're not careful. It can also result in reading entire table(s), possibly inside those nested N+1s. I don't know which "basic mistake" would do this. Maybe when using Lazy loading Proxies? We use EF Core and it is quite easy to control eager loading or load-on-demand on a per-case basis.