Using VARCHAR2 column type fails for Hsqldb running in oracle syntax mode
Description
Environment
Hsqldb 2.3.2 (in oracle syntax mode)
Activity
Show:
Nathan Voxland July 18, 2014 at 6:58 PM
Merged pull request
Anders Lundberg July 6, 2014 at 12:07 PM
A proposed fix is available as a pull request, https://github.com/liquibase/liquibase/pull/284.
Fixed
Details
Details
Reporter
Anders Lundberg
Anders LundbergComponents
Fix versions
Affects versions
Priority
MajorCreated July 5, 2014 at 10:37 AM
Updated July 18, 2014 at 6:58 PM
Resolved July 18, 2014 at 6:58 PM
After migrating to liquibase 3.2.0 (from 2.0.5) our changelog scripts fail on create table when running against Hsqldb, saying
Caused by: org.hsqldb.HsqlException: unexpected token: CHAR required: )
The column causing the problem is defined as VARCHAR2(10 CHAR) but in the generated create table statement it has become VARCHAR(10 CHAR). Liquibase 2.0.5 generates the column correctly, i.e. VARCHAR2(10 CHAR).
Hsqldb is running in oracle syntax mode, enabled by adding sql.syntax_ora=true in the jdbc url.