-
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
Snapshot should preserve the property CLR type when value conversion is used #12212
Labels
closed-fixed
The issue has been fixed and is/will be included in the release indicated by the issue milestone.
type-bug
Milestone
Comments
ajcvickers
changed the title
Snapshot should store column type when value conversion is used
Snapshot should preserve the property CLR type when value conversion is used
Jun 6, 2018
Rather than setting the column type explicitly, which is very provider-specific, we should preserve the property CLR type even when there is a conversion without hints. |
ajcvickers
added
closed-fixed
The issue has been fixed and is/will be included in the release indicated by the issue milestone.
and removed
breaking-change
labels
Jul 6, 2019
ajcvickers
added a commit
that referenced
this issue
Jul 6, 2019
Fixes #16239 Fixes #12212 Also, make the SnapshotModelProcessor finalize the model. I investigated whether it would be better to only store this sometimes, but that then still requires making some assumptions (basically using some conventions and/or the type mapper doing what it does in conventions) when loading the snapshot to ensure we find the right type for the provider being used. Storing it always is clean and simple, decouples from conventions when loading, and means we don't have to do special magic for facets that come from value converters.
ajcvickers
added a commit
that referenced
this issue
Jul 7, 2019
Fixes #16239 Fixes #12212 Also, make the SnapshotModelProcessor finalize the model. I investigated whether it would be better to only store this sometimes, but that then still requires making some assumptions (basically using some conventions and/or the type mapper doing what it does in conventions) when loading the snapshot to ensure we find the right type for the provider being used. Storing it always is clean and simple, decouples from conventions when loading, and means we don't have to do special magic for facets that come from value converters.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
closed-fixed
The issue has been fixed and is/will be included in the release indicated by the issue milestone.
type-bug
If the value converted changes the CLR type and no explicit column type has been set then the snapshot should store the model CLR type as the mapping for the provider CLR type might be different.
See PomeloFoundation/Pomelo.EntityFrameworkCore.MySql#580
The text was updated successfully, but these errors were encountered: