[Mono-bugs] [Bug 60037][Min] Changed - 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 sumadevi@novell.com.

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

--- shadow/60037	2004-06-16 12:37:46.000000000 -0400
+++ shadow/60037.tmp.3928	2004-06-18 02:53:03.000000000 -0400
@@ -1,13 +1,13 @@
 Bug#: 60037
 Product: Mono: Class Libraries
 Version: unspecified
 OS: unknown
 OS Details: Windows XP SP1
-Status: NEW   
-Resolution: 
+Status: RESOLVED   
+Resolution: FIXED
 Severity: Unknown
 Priority: Minor
 Component: Sys.Data.SqlClient
 AssignedTo: sumadevi@novell.com                            
 ReportedBy: cmyers@austin.rr.com               
 QAContact: mono-bugs@ximian.com
@@ -24,6 +24,11 @@
 
 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.
+
+------- Additional Comments From sumadevi@novell.com  2004-06-18 02:53 -------
+SqlCommand.cs - ExecuteNonQuery returns -1 in all cases except
+                insert,update or delete.
+