[release/9.0] Remove referencing indexes when reconfiguring a property as a navigation #34640
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
roji
approved these changes
Sep 10, 2024
SamMonoRT
approved these changes
Sep 10, 2024
artl93
approved these changes
Sep 10, 2024
|
@AndriySvyryd - does this need to go further downward to 8.0? (See #29847) |
AndriySvyryd
force-pushed
the
Issue29997
branch
from
cd99bbf to
48d7bb0
Compare
AndriySvyryd
force-pushed
the
Issue29997
branch
from
48d7bb0 to
58cb4ca
Compare
Yes, #34651 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #29997
Description
When a property is reconfigured as a navigation the referencing objects such as indexes, keys and foreign keys are not removed beforehand leading to an exception.
Customer impact
For models where a navigation is referenced by data annotations an exception is thrown during model building. A workaround is to ignore the property before configuring it as a navigation.
How found
Multiple customer reports.
Regression
Yes. From 6.0.x
Testing
Test added.
Risk
Low.