Skip to content

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

@ajcvickers

Description

@ajcvickers

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.

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions