[Mono-bugs] [Bug 75226][Nor] Changed - [PATCH] System.Data cascading on update triggered too often

[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 george.barbarosie at gmail.com.

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

--- shadow/75226	2005-06-10 20:25:07.000000000 -0400
+++ shadow/75226.tmp.2275	2005-06-10 20:28:24.000000000 -0400
@@ -1,23 +1,23 @@
 Bug#: 75226
 Product: Mono: Class Libraries
 Version: 1.1
-OS: 
+OS: unknown
 OS Details: 
 Status: NEW   
 Resolution: 
-Severity: 
+Severity: Unknown
 Priority: Normal
 Component: Sys.Data
 AssignedTo: mono-bugs at ximian.com                            
 ReportedBy: george.barbarosie at gmail.com               
 QAContact: mono-bugs at ximian.com
 TargetMilestone: ---
 URL: 
 Cc: 
-Summary: System.Data cascading on update triggered too often
+Summary: [PATCH] System.Data cascading on update triggered too often
 
 On svn HEAD, update cascading is triggered even when the fields that
 changed on parent are not referred by another table.
 
 I haven't had a chance to see what MS .NET does in this case, so if anyone
 can test if this is a bigger ADO.NET problem or a MONO specific one, plz do.
@@ -54,6 +54,11 @@
 
 
 ------- Additional Comments From george.barbarosie at gmail.com  2005-06-10 20:25 -------
 Created an attachment (id=15304)
 proposed fix
 
+
+------- Additional Comments From george.barbarosie at gmail.com  2005-06-10 20:28 -------
+fix looks ugly, but without the Type.InvokeMember trick, we cannot
+determine if the two fields contain equal values; simply comparing
+row[src, Proposed] and row[src, Default] won't work.