Status: New
Owner: ----
New issue 108 by cassiot: Constraint update action is always the same of
delete action
http://code.google.com/p/migratordotnet/issues/detail?id=108
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.
Attachments:
TransformationProvider.cs 25.4 KB
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"migratordotnet-devel" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/migratordotnet-devel?hl=en
-~----------~----~----~----~------~----~------~--~---
