[Mono-bugs] [Bug 77630][Nor] New - Cannot remove a UniqueConstraint if any ForeignKeyConstraint exists

bugzilla-daemon at bugzilla.ximian.com bugzilla-daemon at bugzilla.ximian.com
Thu Feb 23 15:50:39 EST 2006

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 prensing at cimetrics.com.


--- shadow/77630	2006-02-23 15:50:39.000000000 -0500
+++ shadow/77630.tmp.4515	2006-02-23 15:50:39.000000000 -0500
@@ -0,0 +1,47 @@
+Bug#: 77630
+Product: Mono: Class Libraries
+Version: 1.1
+OS Details: 
+Status: NEW   
+Priority: Normal
+Component: Sys.Data
+AssignedTo: tsenganal at novell.com                            
+ReportedBy: prensing at cimetrics.com               
+QAContact: mono-bugs at ximian.com
+TargetMilestone: ---
+Summary: Cannot remove a UniqueConstraint if any ForeignKeyConstraint exists
+Please fill in this template when reporting a bug, unless you know what you
+are doing.
+Description of Problem:
+When using a DataSet, I want to check that certain columns in one DataTable
+are unique. To do this, I create a UniqueConstraint and add it to the
+DataTable. I record any errors. I then want to remove the constraint. I do: 
+    dataSet.dataTable.Constraints.Remove( "constraintName" );
+This always fails because it insists that I remove all the foreign key
+constraints first.
+Note that the constraint I am adding is not related to the FK constaints.
+It is probably reasonable to not allow UniqueConstraints to be remove if
+their columns are members of FKs, but this is not the case.
+Steps to reproduce the problem:
+1. Create a data set with a FK relation
+2. Add a UniqueConstraint on some column(s) which are not in the FK
+3. Try to remove it.
+Actual Results:
+Complains that you need to remove the FK constraint first
+Expected Results:
+Removes constraint.
+How often does this happen? 
+Additional Information:

More information about the mono-bugs mailing list