-
Notifications
You must be signed in to change notification settings - Fork 3.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add migrations drop and create foregin key on table that not is modified #3751
Comments
Maybe I can answer it this by myself :) I was adding a navigation property on the base-class for the entities that have tables that ends with "FieldData". But that navigation property was anyway not modifying the database schema. |
I ran diff of both Up & Down methods. |
The cascade delete was on the table before. When inspected the
|
Looks like the model snapshot generator needs to be updated to capture the |
Tested in |
Will send out PR for fix soon. 😄 |
When adding a new migraion a lot of
DropForeginKey
andAddForeginKey
are added even if the table not is touched by the rest of the migration commands. See example theCategoryFieldData
table in the below migration.Is there any reason for this approach?
Using beta8-version.
The text was updated successfully, but these errors were encountered: