Currently (up to 0.20.0BETA) even if you write VARCHAR(1000) the internal datatype is STRING and without any kind of limit on the length of the string.
We should implement this constraint and report it back to JDBC Metadata.
Also we should add some configuration flag to ignore this constraint, in order to preserve backward compatibility: people who migrated their DDL from MySQL probably forgot about that constraint.
Additionally it would be very good for the user to report the name of the column that is failing the constraint check: "error: value 'xxxx' too big for column XXX of type STRING(1234) in table YYYY"
Currently (up to 0.20.0BETA) even if you write VARCHAR(1000) the internal datatype is STRING and without any kind of limit on the length of the string.
We should implement this constraint and report it back to JDBC Metadata.
Also we should add some configuration flag to ignore this constraint, in order to preserve backward compatibility: people who migrated their DDL from MySQL probably forgot about that constraint.
Additionally it would be very good for the user to report the name of the column that is failing the constraint check: "error: value 'xxxx' too big for column XXX of type STRING(1234) in table YYYY"