-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
Add savepoint API to DbTransaction #34561
Conversation
Note regarding the This serves as a reminder for when your PR is modifying a ref *.cs file and adding/modifying public APIs, to please make sure the API implementation in the src *.cs file is documented with triple slash comments, so the PR reviewers can sign off that change. |
Based on the bot's gentle reminder, added triple-slash comments with documentation for the new APIs. Last time I did this, I had to submit a separate PR to https://github.com/dotnet/dotnet-api-docs - has some automatic sync been put into place? If not it may be better not to have the docs here and worry about keeping them in sync... |
src/libraries/System.Data.Common/src/System/Data/Common/DbTransaction.cs
Show resolved
Hide resolved
0853334
to
b8118e7
Compare
b8118e7
to
aa23e4f
Compare
Rebased and made the proper modifications after approval of the design proposal (#33397). |
@ajcvickers ping |
Closes #33397
Note that I've continued the general ADO.NET pattern of having the default implementation of async methods fall back to the sync methods. This also means that the default NotSupportedException gets returned as a failed task rather than a synchronous thrown exception.