Skip to content
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

TransactionScope [DNET307] #320

Closed
firebird-automations opened this issue Apr 6, 2010 · 4 comments
Closed

TransactionScope [DNET307] #320

firebird-automations opened this issue Apr 6, 2010 · 4 comments

Comments

@firebird-automations
Copy link

Submitted by: Alexander Muylaert (alexander_gonline.be)

Relate to DNET337

Hi Jiri

I have noticed that using Transactionscopes results in NO_RECVERSION transactions. Would it be possible to give me a "provider" wide setting to allow me to specify the params of a transaction.

A extra option inside the connectionstring would even be better, but maybe I ask to much now? ;-)

Alexander

@firebird-automations
Copy link
Author

Commented by: @cincuranet

You can specify some options, like IL through TS ctor (http://msdn.microsoft.com/en-us/library/system.transactions.transactionoptions.isolationlevel(v=VS.90).aspx). There's no way to specify some provider specific features, as TS has to work transparently across all providers.

Do you know some other http://ADO.NET provider(s) to support transaction settings via connection string?

@firebird-automations
Copy link
Author

Commented by: @cincuranet

Fixed as a effect of DNET337.

@firebird-automations
Copy link
Author

Modified by: @cincuranet

status: Open [ 1 ] => Resolved [ 5 ]

resolution: Fixed [ 1 ]

Fix Version: 3.0.0.0 [ 10470 ]

@firebird-automations
Copy link
Author

Modified by: @cincuranet

Link: This issue relate to DNET337 [ DNET337 ]

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants