SaveChanges()
.null
for string
, 0
for int
, Guid.Empty
for Guid
, etc.). For more information, see Explicit values for generated properties.GUID
properties (using the SQL Server sequential GUID algorithm). However, if you specify that a DateTime
property is generated on add, then you must setup a way for the values to be generated. One way to do this, is to configure a default value of GETDATE()
, see Default Values.value generated on add
, if you specify a value for the property on a newly added instance of an entity, that value will be inserted rather than a value being generated. It is also possible to set an explicit value when updating. For more information, see Explicit values for generated properties.byte[]
properties that are set as generated on add or update and marked as concurrency tokens, will be setup with the rowversion
data type - so that values will be generated in the database. However, if you specify that a DateTime
property is generated on add or update, then you must setup a way for the values to be generated. One way to do this, is to configure a default value of GETDATE()
(see Default Values) to generate values for new rows. You could then use a database trigger to generate values during updates (such as the following example trigger).