anchor.diff:  (unless an explicit column value had been given), so there should rarely be the need to obtain the default value from the schema.
   Passing the default value helps though with satisfying the compatibility rules when xref:configuration/avro.advoc[using Avro] as serialization format together with the Confluent schema registry.
   
  +[[temporal-values]]
   ==== Temporal values
  +
  +Other than SQL Server's `DATETIMEOFFSET` data type (which contain time zone information), the other temporal types depend on the value of the `time.precision.mode` configuration property.  When the `time.precision.mode` configuration property is set to `adaptive` (the default), then the connector will determine the literal type and semantic type for the temporal types based on the column's data type definition so that events _exactly_ represent the values in the database:
   
   [cols="20%a,15%a,30%a,35%a",width=150,options="header,footer",role="table table-bordered table-striped"]
   |=======================
  
positive.code: Fully-qualified names for columns are of the form _schemaName_._tableName_._columnName_.
  Note that primary key columns are always included in the event's key, also if blacklisted from the value.
  
  |`tombstones.on.delete` +
  0.10.0 and later
  |`true`
  
negative.code: 
  [cols="15%a,15%a,35%a,35%a",width=100,options="header,footer",role="table table-bordered table-striped"]
  |=======================
  |SQL Server Data Type
  |Literal type (schema type)
  |Semantic type (schema name)
  |Notes
  