|
|
|
|
|
|
by setr
16 days ago
|
|
|
> literally save like 20 seconds in some cases because 1 HUGE query becomes 8 straightforward ones with maximum index usage. I don’t understand how splitting a query up would have any relationship to index utilization; the planner should trivially pick up on it? Also are you sure you’re not solving a different problem[0]? Doing joins manually being faster doesn’t smell right, except in the case of data duplication increasing total resultset size substantially Like the cost of increased network load from not filtering through the join should outweigh anything else in the equation https://learn.microsoft.com/en-us/ef/core/querying/single-sp... |
|
|