[Mono-bugs] [Bug 80106][Nor] New - IsolationLevel isn't handled correctly in SqlClient.BeginTransaction

[bugzilla-daemon at bugzilla.ximian.com]

Please do not reply to this email- if you want to comment on the bug, go to the
URL shown below and enter your comments there.

Changed by max at artsalliancelabs.com.

http://bugzilla.ximian.com/show_bug.cgi?id=80106

--- shadow/80106	2006-11-30 18:05:54.000000000 -0500
+++ shadow/80106.tmp.7569	2006-11-30 18:05:54.000000000 -0500
@@ -0,0 +1,38 @@
+Bug#: 80106
+Product: Mono: Class Libraries
+Version: 1.2
+OS: All
+OS Details: 
+Status: NEW   
+Resolution: 
+Severity: 
+Priority: Normal
+Component: Sys.Data.SqlClient
+AssignedTo: mono-bugs at ximian.com                            
+ReportedBy: max at artsalliancelabs.com               
+QAContact: mono-bugs at ximian.com
+TargetMilestone: ---
+URL: 
+Cc: 
+Summary: IsolationLevel isn't handled correctly in SqlClient.BeginTransaction
+
+Our code (which works in MS.Net) is calling
+BeginTransaction(IsolationLevel.Unspecified, null).  According to this
+page, this is valid and "proper" for the default level:
+
+http://msdn2.microsoft.com/en-gb/library/system.data.isolationlevel.aspx
+
+In Mono, this is generating the following invalid SQL:
+
+SET TRANSACTION ISOLATION LEVEL ;BEGIN TRANSACTION 
+
+In SqlConnection.cs Mono has this code:
+
+	tds.Execute (String.Format ("SET TRANSACTION ISOLATION LEVEL {0};BEGIN
+TRANSACTION {1}", isolevel, transactionName));
+
+But isolevel can be String.Empty if it wasn't one of the values in the
+switch...
+
+I assume the fix is adding IsolationLevel.Unspecified below/above
+IsolationLevel.ReadCommitted since that is the default.