Issue Details (XML | Word | Printable)

Key: DNET-307
Type: Improvement Improvement
Status: Resolved Resolved
Resolution: Fixed
Priority: Major Major
Assignee: Jiri Cincura
Reporter: Alexander Muylaert
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
.NET Data provider

TransactionScope

Created: 06/Apr/10 08:58 AM   Updated: 27/Oct/12 07:15 PM
Component/s: ADO.NET Provider
Affects Version/s: None
Fix Version/s: 3.0.0.0

Time Tracking:
Not Specified

Issue Links:
Relate
 


 Description  « Hide
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

 All   Comments   Work Log   Change History   Subversion Commits      Sort Order: Ascending order - Click to sort in descending order
Jiri Cincura added a comment - 06/Apr/10 09:10 AM
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 ADO.NET provider(s) to support transaction settings via connection string?

Jiri Cincura added a comment - 27/Oct/12 07:14 PM
Fixed as a effect of DNET-337.