-
Enhancement
-
Resolution: Unresolved
-
Major
-
None
-
None
-
False
-
None
-
False
-
-
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.