-
Notifications
You must be signed in to change notification settings - Fork 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 some breaking changes #2621
Conversation
entity-framework/core/what-is-new/ef-core-5.0/breaking-changes.md
Outdated
Show resolved
Hide resolved
7009949
to
83d417c
Compare
|
||
**New behavior** | ||
|
||
`IMigrationsModelDiffer` API now uses `IRelationalModel`. However the model snapshot still contains only `IModel` as this code is part of the application and Entity Framework can't change it without making a bigger breaking change. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We still have an issue to update the snapshot, right? I'd really like to do that if we can...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You mean dotnet/efcore#18557? It would still be opt-in, so we'll have to support old snapshots for a while.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Kind of... We could switch to new snapshots only having a RelationalModel but the default implementation could get it from any existing IModel. That command would just help "normalize" old migrations and snapshots.
Fixes #2526
Fixes #2585
Fixes #2225
Fixes #2546