SQL cannot be parsed when using binary type "char (16) for bit data": X'0123' #1089
When using UUIDs in DB2 (or Derby, they are very similar), the column is defined as
Binary literals for CHAR FOR BIT DATA are written like string literals, but with a leading X:
So, when I want to add a new column in a Flyway SQL migration, this syntax is used:
Unfortunately, Flyway does not recognize the
I found no clear documentation for specifying binary literals, but I found a short summary of the most common syntaxes:
Due to this bug, new CHAR FOR BIT DATA columns cannot be added with NOT NULL, because that would require a DEFAULT clause.
The text was updated successfully, but these errors were encountered: