You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Database operation expected to affect 1 row(s) but actually affected 0 row(s). Data may have been modified or deleted since entities were loaded. See http://go.microsoft.com/fwlink/?LinkId=527962 for information on understanding and handling optimistic concurrency exceptions.
I believe that this particular exception message is too general.
Not only other people complained about it ( #17747 (comment) ), but also I think it is kinda misleading (emphasis on concurrency).
Can we receive some more details like... about which entity (idk maybe its id or json dump or something) it is complaining?
I think it'd make migration between EFC versions way easier / less painful
Describe the solution you'd like
More detailed info about why this exception has been thrown.
The text was updated successfully, but these errors were encountered:
Putting on the backlog to consider adding some identifying information in the message when sensitive data logging is enabled. This will primarily be useful for debugging cases where this is not thrown as the result of optimistic concurrency, but rather as a consequence of things like triggers in the database.
AndriySvyryd
changed the title
Data may have been modified or deleted... error should give some details
Improve optimistic concurrency exception
Jan 2, 2024
Hello,
I believe that this particular exception message is too general.
Not only other people complained about it ( #17747 (comment) ), but also I think it is kinda misleading (emphasis on concurrency).
Can we receive some more details like... about which entity (idk maybe its id or json dump or something) it is complaining?
I think it'd make migration between EFC versions way easier / less painful
Describe the solution you'd like
More detailed info about why this exception has been thrown.
The text was updated successfully, but these errors were encountered: