Support ignoring columns with database provided default value
If a database defines a default for a column then the column does not need to be mapped to a conceptual schema property anymore. The column is optional (like nullable columns) and the model should validate even if no mapping for the column is defined.
Possible workaround in less strict but related use-cases: Use a DatabaseGeneratedAttribute with a Computed DatabaseGeneratedOption. Modifying the SSDL directly in non-Code-First scenarios would also do the trick.
If anybody wonders, I think this suggestion is distinctively different than .