[Mono-bugs] [Bug 60037][Min] New - SqlCommand.ExecuteNonQuery behaves differently than MS SqlCommand

[bugzilla-daemon@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 cmyers@austin.rr.com.

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

--- shadow/60037	2004-06-11 11:57:11.000000000 -0400
+++ shadow/60037.tmp.8488	2004-06-11 11:57:11.000000000 -0400
@@ -0,0 +1,29 @@
+Bug#: 60037
+Product: Mono: Class Libraries
+Version: unspecified
+OS: 
+OS Details: Windows XP SP1
+Status: NEW   
+Resolution: 
+Severity: 
+Priority: Minor
+Component: Sys.Data.SqlClient
+AssignedTo: rodrigo@novell.com                            
+ReportedBy: cmyers@austin.rr.com               
+QAContact: mono-bugs@ximian.com
+TargetMilestone: ---
+URL: 
+Cc: 
+Summary: SqlCommand.ExecuteNonQuery behaves differently than MS SqlCommand
+
+Description of Problem:
+If you execute a SELECT statement through an ExecuteNonQuery (I know, "why 
+would you do that", but humor me),
+on MS .NET, the resultant int32 value for rows affected will always be -1, 
+regardless of how many results there were.
+
+However, in Mono, the rows affected is the number of rows returned by the 
+select query.
+
+While I actually prefer how Mono does it, it's inconsistent with MS.NET 
+SqlCommand, so you may want to change this.