[Mono-bugs] [Bug 55162][Blo] Changed - SqlParameter value set to null will not result in NULL in query.

bugzilla-daemon@bugzilla.ximian.com bugzilla-daemon@bugzilla.ximian.com
Tue, 30 Mar 2004 11:27:50 -0500 (EST)

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 lluis@ximian.com.


--- shadow/55162	2004-03-04 11:08:05.000000000 -0500
+++ shadow/55162.tmp.5040	2004-03-30 11:27:50.000000000 -0500
@@ -1,14 +1,14 @@
 Bug#: 55162
-Product: Mono/Class Libraries
+Product: Mono: Class Libraries
 Version: unspecified
+OS: unknown
 OS Details: XP sp1
 Status: NEW   
+Severity: Unknown
 Priority: Blocker
 Component: Sys.Data.SqlClient
 AssignedTo: rodrigo@ximian.com                            
 ReportedBy: frans@sd.nl               
 QAContact: mono-bugs@ximian.com
 TargetMilestone: ---
@@ -43,6 +43,9 @@
 Additional Information:
 the sql query is generated at runtime, so are the parameters, this is why
 the value null is required to signal NULL. This works in the .NET sqlserver
 client and the Oracle ODP.NET client without a problem. If this doesn't
 work on Mono, it will make porting code to Mono harder.
+------- Additional Comments From lluis@ximian.com  2004-03-30 11:27 -------
+Can you post a simple test case? It would be of great help.