As announced at the beginning of this week, I have now released version 1.5.4. The benefits of delaying this release just a little are the inclusion of various important bugfixes related to code generation for the Oracle dialect (and potentially others), thanks to reports given by Hy.
As in most releases, a new SQL dialect is supported: Derby. jOOQ proves to be effective when you migrate your database to Derby, as Derby knows one of the most restrictive type systems in the RDBMS world. If you are not used to that strong kind of typing, jOOQ will help you out by automatically casting bind variables, values, and procedure parameters to the expected type just as with the DB2 dialect. If automatic casting is not sufficient, you can now also explicitly cast to both Java types and dialect-specific types. Some examples: - field.cast(String.class) casts field to the default type for the String class - field.cast(OracleDataTypes.VARCHAR2) casts field to an Oracle VARCHAR2 type The latter example shows that jOOQ now fully supports dialect-specific data types, not just automatic mappings. Apart from those data types, also ARRAY types are supported in Oracle, Postgres, HSQLDB and H2 dialects. ARRAY types are intuitively bound to the Field's <T> generic type. Check out the Examples page in the following days, to see a more detailed documentation about recent updates to jOOQ: https://sourceforge.net/apps/trac/jooq/wiki/Examples Please note: when you update to this release, you will need to regenerated your database meta model, as there is a minor API change in the model's base classes due to the support of dialect-specific data types. Please report any issues you may encounter here: https://sourceforge.net/apps/trac/jooq/newticket Have fun and a happy weekend! Lukas
