Describe the bug
Updates the child model elements when using the parent ModelWriterService implementation fails because one row is expected to be modified, but zero actually are.
To Reproduce
Steps to reproduce the behavior:
Load aInvestmentStrategy instance with child InvestmentStrategyTarget instances.
Update attributes of the child models.
Save the InvestmentStrategy instance using ModelWriterServer.UpdateAsync method.
See DbUpdateConcurrencyException with the following error message:
The database operation was expected to affect 1 row(s), but actually affected 0 row(s); data may have been modified or deleted since entities were loaded.
Expected behavior
The update action should account for related records, and update the entire attached object graph.
Additional context
First identified in commit 3a526f4b71cf70cc65c2f4a1a88a44b0e773392e.
Describe the bug Updates the child model elements when using the parent
ModelWriterService
implementation fails because one row is expected to be modified, but zero actually are.To Reproduce Steps to reproduce the behavior:
InvestmentStrategy
instance with childInvestmentStrategyTarget
instances.InvestmentStrategy
instance usingModelWriterServer.UpdateAsync
method.DbUpdateConcurrencyException
with the following error message:Expected behavior The update action should account for related records, and update the entire attached object graph.
Additional context First identified in commit 3a526f4b71cf70cc65c2f4a1a88a44b0e773392e.