New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Risk using async trigger behind a sync SaveChanges() call? #127
Comments
cc: @anthony-keller |
There is indeed a risk as calls to Hope this helps! |
Thanks @koenbeuk , good to know. I think I might make a concerted effort to async all our things to be sure. It might be worth linking this issue from a disclaimer on the readme/docs if you think it warrants it. |
@benmccallum I'm open for that. Would you mind issuing a PR? |
Hey! We've still got plenty of sync
SaveChanges()
calls in our codebase that we're slowly getting rid of but it did make me wonder whether there's a risk to writing an async trigger behind a sync call.Before we dive in fully we might need to eliminate all our legacy sync SaveChanges() calls.
The text was updated successfully, but these errors were encountered: