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
We are using .netcore 2.2
We are adding a trigger to the updating action and another trigger (GlobalUpdateFailed) to undo what the updating trigger does when the DB Save fails. We try to attempt a DB save with a read only dbuser it throws a DBUpdateException but when RaiseFailedEventsAsync is called there is a check for the number of entries in the changetracker and if it is not 1 it exits without calling the GlobalUpdateFailed trigger. Can you please help us understand the reason for the check.
In our application, we try to make our DB changes transactional, in this one action we indeed change a few DB entries but we only call DB save once to ensure the DB integrity and increase performance.
The text was updated successfully, but these errors were encountered:
The following method located in "EntityFramework.Triggers/src/EntityFrameworkCore.Triggers/TriggerInvokerAsync.cs" returns false instead of await RaiseFailedEventsInternalAsync(context, serviceProvider, entries, dbUpdateException); when the number of entries is not 1. However our entries are greater than 1. Therefore we were wondering why you are checking the number of entries since it would be important for us to have the revert for entries that are greater than 1.
We are using .netcore 2.2
We are adding a trigger to the updating action and another trigger (GlobalUpdateFailed) to undo what the updating trigger does when the DB Save fails. We try to attempt a DB save with a read only dbuser it throws a DBUpdateException but when RaiseFailedEventsAsync is called there is a check for the number of entries in the changetracker and if it is not 1 it exits without calling the GlobalUpdateFailed trigger. Can you please help us understand the reason for the check.
In our application, we try to make our DB changes transactional, in this one action we indeed change a few DB entries but we only call DB save once to ensure the DB integrity and increase performance.
The text was updated successfully, but these errors were encountered: