You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Starting in RC1 - cascade delete is on by default for all required relationships (this is the same behavior as EF6 and we were just waiting for cascade delete to be implemented to enable it). After aligning the schema with the new convention, you may still hit issue #3751 where migrations will continually try to drop and re-create foreign keys because it thinks the cascade behavior has changed. This is fixed in our current code base (and will ship in RC2).
When I do this in EF 7 RC1
I just change On Delete Cascade for ONE table.
When I look at the migration code, all tables Referential Integrity is changed ???
from ReferentialAction.Restrict to Cascade !!!
The text was updated successfully, but these errors were encountered: