Adding a foreign key is possible to define the foreign key constraints like
ForeignKeyConstraint.Cascade. The problem is that the definition is always
the same for delete and update.
I don't know by the others but most of the time that I define a cascade is
only for delete. I never define the cascade to an update and it always is
restrict.
I modified the method AddForeignKey to not set the update action for a
constraint. I am attaching my TransformationProvider.cs file with this
simple modification.
Maybe the best option is to have another overload of this method where we
can define both option. It's up to you.
Original issue reported on code.google.com by cass...@gmail.com on 14 Apr 2009 at 2:27
Original issue reported on code.google.com by
cass...@gmail.com
on 14 Apr 2009 at 2:27Attachments: