I have released jOOQ 2.5.2 and 2.6.1 with minor patches. These bug fixes will are also available in a future 2.7.0 and 3.0.0 version
More details can be seen here: - http://www.jooq.org/notes.php?version=2.5 - http://www.jooq.org/notes.php?version=2.6 Older branches will not be patched unless requested specifically. Version 2.6.1 - December 27, 2012 ================================================================================ This is a minor patch release with some useful fixes for the 2.6 branch Bug fixes --------- #1890 - Bad Postgres array serialisation when " or \ characters are contained in a String[] #1937 - Inefficient implementations of AbstractDataType.equals() and hashCode() #1938 - Improve AbstractField.hashCode() and AbstractTable.hashCode() and similar, as these two are called very often #1942 - Inefficient call to String.split() in StringUtils.toCamelCase() leads to non-negligible performance ovrerhead in POJO transformation calls #1954 - Bad SQL rendered when combining ORDER BY [ some-function ] with LIMIT .. OFFSET in DB2, SQL Server #1958 - Bad SQL rendered for OVER (ORDER BY [ some-function ]) for SQL Server and Sybase #1979 - Thread safety issue in org.jooq.impl.FieldList #1992 - Bad reference to org.jooq.debug.[impl].DebugListener in the manual #1993 - Bad code generated when the same table name exists in multiple schemas in SQL Server #1995 - Record.original() values aren't updated after a Record.store() operation #2007 - Bad type coercion on the right hand side of a comparison predicate, when the left hand side is Field<Object> #2011 - Implement some micro-optimisations in DefaultRenderContext #2045 - Bad hashCode calculation when Records contain arrays or byte[] Version 2.5.2 - December 27, 2012 ================================================================= This is a minor patch release with some useful fixes for the 2.5 branch Bug fixes --------- #1850 - Record.equals() returns true as soon as both records hold a "null" value for a given field #1876 - NULL constraint violation when storing a copied record #1890 - Bad Postgres array serialisation when " or \ characters are contained in a String[] #1937 - Inefficient implementations of AbstractDataType.equals() and hashCode() #1938 - Improve AbstractField.hashCode() and AbstractTable.hashCode() and similar, as these two are called very often #1942 - Inefficient call to String.split() in StringUtils.toCamelCase() leads to non-negligible performance overhead in POJO transformation calls #1954 - Bad SQL rendered when combining ORDER BY [ some-function ] with LIMIT .. OFFSET in DB2, SQL Server #1960 - Bad SQL rendered for OVER (ORDER BY [ some-function ]) for SQL Server and Sybase #1979 - Thread safety issue in org.jooq.impl.FieldList #1993 - Bad code generated when the same table name exists in multiple schemas in SQL Server #2007 - Bad type coercion on the right hand side of a comparison predicate, when the left hand side is Field<Object> #2011 - Implement some micro-optimisations in DefaultRenderContext
