Re: [Hsqldb-user] Varchar and Varchar(size) implementation issues

[Lorna B. <lor...@sa...>]

Up to and including HSQLDB 1.8.0.7, VARCHAR (without the length declaration) is a synonym for VARCHAR(MAX) where 'MAX' is the special keyword that denotes the maximum length in context of the given SQL type.

Other than that, when the database property "sql.enforce_strict_size" is set TRUE, HSQLDB CHAR behaves like standards CHAR [ACTER] type (fixed-length, padding semantics, error on data truncation) and HSQLDB VARCHAR behaves like standards VARCHAR (variable-length, non-padded semantics, error on data truncation)

When the database property "sql.enforce_strict_size" is set FALSE, HSQLDB CHAR and VARCHAR behave mostly like java.lang.String (variable length, no padding, no length check, lenght declaration ignored and Integer.MAX_VALUE is always 'effective' max length).

See:  http://hsqldb.org/doc/guide/ch04.html#N10C42