Skip to content
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

[6.0.1] Match indexer properties correctly #26645

Merged
merged 3 commits into from
Nov 15, 2021
Merged

Conversation

AndriySvyryd
Copy link
Member

Fixes #26590

Description

When an FK attribute is used with a property on a property bag entity type EF ends up creating a property with a uniquified name instead of using the specified one.

This is made worse in 6.0 because now EF scaffolds this type of configuration for existing databases.

Customer impact

User queries will throw exception since the new property doesn't match a column in the database

How found

Customer reported on 6.0

Regression

Yes, this worked in 5.0

Testing

Added test for this scenario.

Risk

Low, only affects property bag entities (Dictionary<string, object>). Also added a quirk mode.

@AndriySvyryd AndriySvyryd added this to the 6.0.x milestone Nov 12, 2021
@AndriySvyryd AndriySvyryd requested a review from a team November 12, 2021 05:59
@AndriySvyryd AndriySvyryd changed the title [6.0.1] Match indexer properties correctly Match indexer properties correctly Nov 15, 2021
@AndriySvyryd AndriySvyryd merged commit 6833c43 into release/6.0 Nov 15, 2021
@AndriySvyryd AndriySvyryd deleted the Issue26590 branch November 15, 2021 20:01
@ajcvickers ajcvickers removed this from the 6.0.x milestone Nov 17, 2021
@ajcvickers ajcvickers changed the title Match indexer properties correctly [6.0.1] Match indexer properties correctly Nov 17, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants