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

Ensure that facets specified in the store type name take precedence #29628

Merged
merged 3 commits into from
Nov 30, 2022

Conversation

ajcvickers
Copy link
Member

Fixes #29600.

Using a store type name always overrides any other configuration of the type, since it is has ultimate fidelity of what the database supports. Previously, we were overriding facets set in the store type with those configured by data annotations of the model building API.

This change uses -1 to represent an explicitly configured "max" length, as opposed to no length configured, which is consistent with ADO.NET and EF6. Filed #29627 to make this first-class.

Fixes #29600.

Using a store type name always overrides any other configuration of the type, since it is has ultimate fidelity of what the database supports. Previously, we were overriding facets set in the store type with those configured by data annotations of the model building API.

This change uses -1 to represent an explicitly configured "max" length, as opposed to no length configured, which is consistent with ADO.NET and EF6. Filed #29627 to make this first-class.
@ajcvickers ajcvickers requested a review from a team November 20, 2022 10:03
ajcvickers and others added 2 commits November 30, 2022 10:50
Co-authored-by: Andriy Svyryd <AndriySvyryd@users.noreply.github.com>
Co-authored-by: Andriy Svyryd <AndriySvyryd@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

HasPrecision overrides precision set in explicit store type
2 participants