Hello jOOQ-community I have noticed some serious issues when upgrading HSQLDB from 2.0.0 to 2.1.0. These are some of the main issues:
- There is an HSQLDB-Bug when casting to LONGVARCHAR, which was jOOQ's primary mapping for String columns. This pretty much blocks using jOOQ altogether - LONGVARCHAR cannot be mapped to String anymore, as INFORMATION_SCHEMA views incompatibly map this type to the new CHARACTER LARGE OBJECT type - LONGVARBINARY cannot be mapped to byte[] anymore, as INFORMATION_SCHEMA views incompatibly map this type to the new BINARY LARGE OBJECT type I have immediately reported these issues to Fred Toussi. In the mean time, please don't upgrade to 2.1.0 before I release jOOQ 1.5.7, fixing these issues: https://sourceforge.net/apps/trac/jooq/ticket/386 I plan to release 1.5.7 early, some time next week, also to fix some issues regarding serialisation: https://sourceforge.net/apps/trac/jooq/ticket/380 Cheers Lukas
