anchor.diff:   +
   Represents the number of microseconds past epoch, and does not include timezone information.
   
  -|`TIMESTAMP(7 - 9)` +
  - |`INT64`
  +|`TIMESTAMP(7 - 9)`
  +|`INT64`
   |`io.debezium.time.NanoTimestamp` +
    +
   Represents the number of nanoseconds past epoch, and does not include timezone information.
  
positive.code: |`STRING`
  |`io.debezium.time.ZonedTimestamp` +
   +
  A string representation of a timestamp with timezone information
  
  |`TIMESTAMP WITH LOCAL TIME ZONE`
  |`STRING`
  |`io.debezium.time.ZonedTimestamp` +
   +
  A string representation of a timestamp with timezone information
  
  |===
  
  
negative.code: [id="oracle-temporal-types"]
  === Temporal types
  
  Other than Oracle's `INTERVAL`, `TIMESTAMP WITH TIME ZONE` and `TIMESTAMP WITH LOCAL TIME ZONE` data types, 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 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="25%a,20%a,55%a",options="header"]
  |===
  |Oracle data type |Literal type (schema type) |Semantic type (schema name) and Notes
  