-
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
Allow applications to force nullability of columns #24685
Comments
Note from triage: Ping @AndriySvyryd when working on this. |
Add |
@ajcvickers I have the exact same issue as in [#27227] (#27227) and have tried to use this as the solution but no joy. I have an entity, MyEntity with a property defined as follows:
In ConfigureMappings, I am setting
but I get the following exception:
at
Should I expect this to work now or has the support for this been reverted? |
@nettashamir-allocate This is the issue tracking the scenario you describe. |
Note to implementer: the main usage to be updated is
|
Note from triage: Implement this through #27970. |
Split off from #13850
By default, a column is nullable in the database if the property to which it is mapped is nullable. This is true even if the converter itself never converts nulls, since by default nulls are passed through unconverted. However, if the value converter converts nulls and ensures that no null values result from this conversion, then it it can make sense for the database column to be non-nullable.
The text was updated successfully, but these errors were encountered: