Hi my friends, Just a short note to advertise my upcoming release 1.5.4, whose scope has been finalised. I would have liked to add many more features on the DSL-side, which have been postponed to 1.5.5, as developments in casting have proven more complex than I thought initially.
Apart from the previously announced features, these will be the main ones included in release 1.5.4: - Support for ARRAY, VARRAY types starting with (and various subsequent tickets): https://sourceforge.net/apps/trac/jooq/ticket/163 ARRAY types might not be very wide-spread. This is probably due for two reasons. 1. They don't fit in well with a relational model. They are hard to use for joins, compares, order by clauses, etc. 2. JDBC support is non-trivial. Depending on the dialect, you may or may not be able to just pass a Java array to the setObject() methods, or receive such an array from the getObject() methods. Many dialects, however, depend on the JDBC-type java.sql.Array, which cannot be constructed with JDBC (e.g. Oracle). jOOQ provides a unified API based on the Field<T> type, where you will be able to use Field<T[]> fields and all their respective properties. - Support for casting: https://sourceforge.net/apps/trac/jooq/ticket/215 https://sourceforge.net/apps/trac/jooq/ticket/246 While casting to a Java object (Field.cast(Class type)) was fairly obvious to implement, casting for the newly refactored DataType<T> is more complex. Several past issues related to type-less null values (DB2, Derby) and other things can be resolved with casting. Most of the time, jOOQ will still do the necessary casting for you, depending on the dialect. But sometimes this is not possible. That's where you as the user can cast explicitly. Looking forward to the upcoming release Cheers Lukas
