Test for transaction rollback on procedure with specified schema #358
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Hi, We are experiencing an issue with rolling back a transaction which executes a stored procedure in a schema other than dbo. I have created a test that reproduces the issue: even if the schema is dbo, by specifying it explicitly we lose the transaction. I followed the code through as far as DynamicSchema.TryInvokeMember calling command.Execute without passing any transaction? That's as far as I got, but I could be going down completely the wrong rabbit hole... I'd be happy to (try to) help further if you agree this is in need of fixing! Tim
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi,
We are experiencing an issue with rolling back a transaction which executes a stored procedure in a schema other than dbo. I have created a test that reproduces the issue: even if the schema is dbo, by specifying it explicitly we lose the transaction.
I followed the code through as far as DynamicSchema.TryInvokeMember calling command.Execute without passing any transaction? That's as far as I got, but I could be going down completely the wrong rabbit hole... I'd be happy to (try to) help further if you agree this is in need of fixing!
Tim