Uploaded image for project: 'Debezium'
  1. Debezium
  2. DBZ-7933

SQL Server default value resolution for TIME data types causes precision loss

XMLWordPrintable

      The SqlServerDefaultValueConverter uses ResultSet#getTime rather than ResultSet#getTimestamp which unnecessarily truncates precision beyond TIME(3).
      See https://debezium.zulipchat.com/#narrow/stream/348252-community-sqlserver/topic/value.20for.20column.20of.20TIME.20datatype.20not.20geting.20loaded.20properly/near/443328357

            ccranfor@redhat.com Chris Cranford
            ccranfor@redhat.com Chris Cranford
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: