Allow ExecuteUpdate to update properties of multiple queries as long as they map to a single table #31406
Labels
area-bulkcud
closed-fixed
The issue has been fixed and is/will be included in the release indicated by the issue milestone.
type-enhancement
Milestone
Our current ExecuteUpdate logic checks that only one entity type is updated by all the setters; this blocks scenarios such as the following:
Updating columns mapped to multiple owned entities (and the owner):
(note: this will also apply to complex types)
Updating columns mapped to a single table within a TPT hierarchy:
Updating the main table of an entity with entity splitting
As long as updates only affect columns on the main table, this now works.
Unfortunately, updates to any of the split tables fail on SQL Server for other, architectural reasons, see #31407. On Sqlite they pass, because a different query shape is generated.
The text was updated successfully, but these errors were encountered: