[Mono-bugs] [Bug 74924][Maj] Changed - DataSet cascading not working on change

[bugzilla-daemon@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@gmail.com.

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

--- shadow/74924	2005-05-12 09:28:59.000000000 -0400
+++ shadow/74924.tmp.5488	2005-05-12 09:39:17.000000000 -0400
@@ -1,14 +1,14 @@
 Bug#: 74924
 Product: Mono: Class Libraries
 Version: 1.1
-OS: 
+OS: unknown
 OS Details: Gentoo Linux 2004.0 ~x86
 Status: NEW   
 Resolution: 
-Severity: 
+Severity: Unknown
 Priority: Major
 Component: Sys.Data
 AssignedTo: mono-bugs@ximian.com                            
 ReportedBy: george.barbarosie@gmail.com               
 QAContact: mono-bugs@ximian.com
 TargetMilestone: ---
@@ -30,6 +30,18 @@
 I will attach sample code.
 
 ------- Additional Comments From george.barbarosie@gmail.com  2005-05-12 09:28 -------
 Created an attachment (id=15130)
 test case / sample code; modifying clients.id does not propagate to orders.client
 
+
+------- Additional Comments From george.barbarosie@gmail.com  2005-05-12 09:39 -------
+As a side effect of this, getting a data adaptor to update
+autoincrement fields back from database to dataset on insert and
+update no longer works for datasets containing foreign keys;
+
+Imagine you add a row in the primary table (clients) and a row in
+child table (orders) referencing the new client. When submitting
+changes in clients the new row gets a new primary key (autoincrement),
+but the order still references a now inexistent client. When
+submitting changes in orders you generate a foreign key violation in
+the database backed.