Bug #22528 | TransactionScope does not work in 5 | ||
---|---|---|---|
Submitted: | 20 Sep 2006 18:07 | Modified: | 21 Jan 2014 23:02 |
Reporter: | [ name withheld ] | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | Connector / NET | Severity: | S1 (Critical) |
Version: | 5 | OS: | Windows (Windows XP) |
Assigned to: | CPU Architecture: | Any |
[20 Sep 2006 18:07]
[ name withheld ]
[21 Sep 2006 14:16]
[ name withheld ]
I went under the assumption that MySqlConnection simply wasn't auto-enlisting in the enclosing transaction, and so I tried to manually enlist a new connection when I created it; however, this did not work. Transaction currentTransaction = Transaction.Current; if (currentTransaction != null && retConnection is MySqlConnection) { // MySQL does not support auto-enlist yet retConnection.EnlistTransaction(currentTransaction); }
[30 Sep 2006 10:11]
Tonci Grgin
Hi. I will quote Reggie on this: "5.0.0 supports TransactionScope. It does not yet support upgrading transactions to full MSDTC scope. We are working on supporting this in the 5.0.2 release."
[30 Sep 2006 14:14]
[ name withheld ]
I don't believe this has anything to do with MSDTC, this is not a distributed transaction, but a simple local transaction on the same data source. If 5.0.0 supports TransactionScope, then I imagine this is a bug. Perhaps my setup is just wrong, but I have tried many options, and I cannot get a simple, *local* TransactionScope to work... Thanks