Skip to content

Conversation

@roji
Copy link
Member

@roji roji commented Apr 5, 2020

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.

@Dotnet-GitSync-Bot
Copy link
Collaborator

Note regarding the new-api-needs-documentation label:

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.

@roji
Copy link
Member Author

roji commented Apr 5, 2020

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...

@roji roji force-pushed the SystemDataSavepoints branch from b8118e7 to aa23e4f Compare July 31, 2020 11:44
@roji
Copy link
Member Author

roji commented Jul 31, 2020

Rebased and made the proper modifications after approval of the design proposal (#33397).

@roji roji requested a review from ajcvickers July 31, 2020 11:45
@roji
Copy link
Member Author

roji commented Aug 5, 2020

@ajcvickers ping

@roji roji merged commit 8250b0a into dotnet:master Aug 5, 2020
Jacksondr5 pushed a commit to Jacksondr5/runtime that referenced this pull request Aug 10, 2020
@ghost ghost locked as resolved and limited conversation to collaborators Dec 9, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Expose transaction savepoints in ADO.NET

5 participants