[Mono-bugs] [Bug 73587][Maj] Changed - DbDataAdapter.Update(...) doesn't respect all properties it should

bugzilla-daemon@bugzilla.ximian.com bugzilla-daemon@bugzilla.ximian.com
Tue, 22 Mar 2005 13:26:53 -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 mono@rankweg.ch.

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

--- shadow/73587	2005-03-22 07:49:11.000000000 -0500
+++ shadow/73587.tmp.10630	2005-03-22 13:26:53.000000000 -0500
@@ -1,13 +1,13 @@
 Bug#: 73587
 Product: Mono: Class Libraries
 Version: unspecified
 OS: All
 OS Details: 
-Status: RESOLVED   
-Resolution: FIXED
+Status: REOPENED   
+Resolution: 
 Severity: Unknown
 Priority: Major
 Component: Sys.Data
 AssignedTo: tsureshkumar@novell.com                            
 ReportedBy: mono@rankweg.ch               
 QAContact: mono-bugs@ximian.com
@@ -47,6 +47,30 @@
 ------- Additional Comments From tsureshkumar@novell.com  2005-03-22 07:49 -------
 fixed in svn head.
 
 thanks for the patch.
 
 suresh.
+
+------- Additional Comments From mono@rankweg.ch  2005-03-22 13:26 -------
+There are still bugs with the RowUpdatedEventArgs.Staus-Property:
+- The changes are per default accepted
+  -> Line 830
+- In case UpdateStatus.SkipAllRemainingRows the changes are accepted,
+but the Docs specify clearly that the changes are not to be accepted.
+  -> Line 827
+
+Note: The Microsoft implementation also behaves incorrectly. I filed a
+bug at Microsoft report too
+(http://lab.msdn.microsoft.com/productfeedback/viewfeedback.aspx?feedbackId=71b2c81e-f4c6-4bf2-9de9-2d28d7be2896).
+
+Meanwhile, I found also two other bugs on the backmapping of the
+values from the parameter or resultset:
+- If a column is ReadOnly the backmappings doesn't work
+  -> Resolution: clear ReadOnly, write value, reset to read only
+- The SourceColumn-Property doesn't handle null or empty values
+  -> Resolution: Check if its empty
+
+Both around lines  781 (resulset) and 811 (parameters)
+
+Please also note that the whole behavior changes again in .NET 2.0
+with the introduction of the new property 'AcceptChangesDuringUpdate'.