[Mono-bugs] [Bug 77480][Nor] New - DBDataAdapter is setting schema NotNull on columns when Fill is called, but not setting DefaultValue

[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 michael at codecobblers.com.

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

--- shadow/77480	2006-02-06 00:39:23.000000000 -0500
+++ shadow/77480.tmp.30945	2006-02-06 00:39:23.000000000 -0500
@@ -0,0 +1,44 @@
+Bug#: 77480
+Product: Mono: Class Libraries
+Version: unspecified
+OS: Red Hat 9.0
+OS Details: 
+Status: NEW   
+Resolution: 
+Severity: 
+Priority: Normal
+Component: Sys.Data
+AssignedTo: tsenganal at novell.com                            
+ReportedBy: michael at codecobblers.com               
+QAContact: mono-bugs at ximian.com
+TargetMilestone: ---
+URL: 
+Cc: 
+Summary: DBDataAdapter is setting schema NotNull on columns when Fill is called, but not setting DefaultValue
+
+Please fill in this template when reporting a bug, unless you know what you
+are doing.
+Description of Problem:
+In version 1.1.13, the DBDataAdapter is retrieving the SQL schema and
+setting the NotNull flag on the columns of the table when Fill is called. 
+It is not setting the DefaultValue.  It should not be setting either one
+unless the caller has specified to do so.
+
+Steps to reproduce the problem:
+1. Create a DBDataAdapter (from whatever connector used to access SQL)
+2. Fill a DataTable using a select from a SQL table which has a column that
+is marked NotNull, but is not a Primary Key
+3. Insert a new row in the resultant DataTable, but do not set that column.
+ Mono 1.1.13 will generate an exception that the column in question cannot
+be null.  This worked correctly in 1.1.10
+
+Actual Results:
+Exception
+
+Expected Results:
+Inserting new row works
+
+How often does this happen? 
+100%
+
+Additional Information: