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

SQL Server varbinary(max), varchar(max), and nvarchar(max) should use unavailable.value.placeholder

    XMLWordPrintable

Details

    • Enhancement
    • Resolution: Unresolved
    • Major
    • 2.6.0.Beta1
    • None
    • sqlserver-connector
    • None
    • False
    • None
    • False

    Description

      When an UPDATE is applied on a table that has a VARBINARY(MAX), VARCHAR(MAX), or NVARCHAR(MAX) data type, the column will be assigned NULL in the capture table.

      We should treat these column mappings identical to PostgreSQL TOAST columns or Oracle's BLOB/CLOB columns where if the value isn't being set, we should perhaps expose these using the unavailable.value.placeholder concept.

      Open question is whether we can determine if the column being NULL in the capture table is actually distinguishable from the user explicitly setting the column as NULL vs it being NULL due to the fact the column wasn't changed.

      https://debezium.zulipchat.com/#narrow/stream/348252-community-sqlserver/topic/error.20varchar.28max.29/near/390307416

      Attachments

        Activity

          People

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

            Dates

              Created:
              Updated: