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.

Sign up for GitHub

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

Jump to bottom

Separate column default constraints from EF store-generated values #13224

Open
ajcvickers opened this issue Sep 5, 2018 · 2 comments
Open

Separate column default constraints from EF store-generated values #13224

ajcvickers opened this issue Sep 5, 2018 · 2 comments
Assignees
@ajcvickers
Labels
area-change-tracking type-enhancement
Milestone
Backlog

Comments

@ajcvickers
Copy link
Member

Issue #9627 talked about the different possible reasons for having columns with default constraints. We discussed this some more and decided to look at adding more separation of these concepts in the 3.0 timeframe. This would make it easier to specify that a column has a default constraint without that meaning that EF should use a sentinel value to decide whether or not to include a value for the column.
@ajcvickers ajcvickers added this to the 3.0.0 milestone Sep 5, 2018
@ajcvickers ajcvickers self-assigned this Sep 5, 2018
@ajcvickers ajcvickers mentioned this issue Sep 5, 2018
Closed
@AndriySvyryd
Copy link
Member

Related to #701

@ajcvickers
Copy link
Member Author

Notes from planning:

  • We can probably do this without it being a breaking change, possibly with new API
  • This is mostly a reverse engineering issue, for which we have already mitigated the CLR default case.
  • We have other ideas around reverse engineering patterns that could further mitigate.
    Therefore. moving to Backlog for now.

@ajcvickers ajcvickers modified the milestones: 3.0.0, Backlog Jan 25, 2019
ajcvickers added a commit that referenced this issue Apr 25, 2023
@ajcvickers
Allow configuration of the sentinel value that indicates a property h…
783ed04 
…as not been set

Fixes #701

Part of #13224, #15070, #13613

This PR contains the underlying model and change tracking changes needed to support sentinel values. Future PRs will add model building API surface and setting the sentinel automatically based on the database default.

There is a breaking change here: explicitly setting the value of a property with a temporary value no longer automatically makes the value non temporary.
@ajcvickers ajcvickers mentioned this issue Apr 25, 2023
Merged
ajcvickers added a commit that referenced this issue Apr 28, 2023
@ajcvickers
Allow configuration of the sentinel value that indicates a property h…
e1fedf2 
…as not been set

Fixes #701

Part of #13224, #15070, #13613

This PR contains the underlying model and change tracking changes needed to support sentinel values. Future PRs will add model building API surface and setting the sentinel automatically based on the database default.

There is a breaking change here: explicitly setting the value of a property with a temporary value no longer automatically makes the value non temporary.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@ajcvickers ajcvickers

Labels
area-change-tracking type-enhancement
Projects
None yet
Milestone
Backlog
Development

No branches or pull requests
2 participants
@ajcvickers @AndriySvyryd