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 [EMAIL PROTECTED] http://bugzilla.ximian.com/show_bug.cgi?id=75226 --- shadow/75226 2005-06-10 20:28:24.000000000 -0400 +++ shadow/75226.tmp.19170 2005-06-11 17:13:55.000000000 -0400 @@ -59,6 +59,11 @@ ------- Additional Comments From [EMAIL PROTECTED] 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. + +------- Additional Comments From [EMAIL PROTECTED] 2005-06-11 17:13 ------- +I've asked a friend to check this bug on MS .NET and it looks like +they do the right thing, i.e. they check that the foreign key fields +have actually changed before cascading on update. This is a MONO bug. _______________________________________________ mono-bugs maillist - [email protected] http://lists.ximian.com/mailman/listinfo/mono-bugs
