I just ran into trouble trying to execute some very basic samples from the first chapter of the manual because in-memory provider doesn't support rollback. Wouldn't it be nice to throw informative exception when one tries to create nested transaction since it's not really supported?

If it's too much of trouble to prohibit customer from execute valid code for standalone provider because it's such an important usecase, might just throw that informative exception when actual rollback has to occure?

I mean

var nestedScope = Transaction.Open(TransactionOpenMode.New);
// As we rollback on in-memory provider throw here
nestedScope.Dispose();

This thread was imported from our support forum. The original discussion may contain more detailed answer. Original topic by marmon.

asked Jul 01 '10 at 10:46

Editor's gravatar image

Editor
46139156157

edited Oct 27 '10 at 09:21

Alex%20Yakunin's gravatar image

Alex Yakunin
29714412

Great idea.

  • We'll add an option to its connection URL that will prevent exceptions on rollback (for our own tests, etc.).
(Jul 01 '10 at 10:46) Alex Yakunin Alex%20Yakunin's gravatar image

One Answer:

Issue 722 is fixed.

answered Oct 27 '10 at 09:14

Alex%20Yakunin's gravatar image

Alex Yakunin
29714412

Your answer
Please start posting your answer anonymously - your answer will be saved within the current session and published after you log in or create a new account. Please try to give a substantial answer, for discussions, please use comments and please do remember to vote (after you log in)!
toggle preview

Subscription:

Once you sign in you will be able to subscribe for any updates here

Tags:

×568
×7
×7

Asked: Jul 01 '10 at 10:46

Seen: 2,189 times

Last updated: Oct 27 '10 at 09:21

powered by OSQA