Use IN instead of EXISTS with ExecuteDelete and entity containment #31386
Labels
area-bulkcud
area-perf
closed-fixed
The issue has been fixed and is/will be included in the release indicated by the issue milestone.
type-enhancement
Milestone
When the base query is complex and can't be natively translated to DELETE, we fall back to placing it in a subquery and deleting all rows where the IDs match. For example, we currently generate:
As we've seen in #30955, doing the same thing with IN can be far more efficient.
The text was updated successfully, but these errors were encountered: