Release Notes: This is a maintenance release for jOOQ 2.0. The main improvements include better integration for using jOOQ with Spring Data. This includes support for named parameters, as well as allowing you to change bind values on previously constructed Query objects. The MERGE statement has been enhanced for better integration with Oracle. jOOQ is now ready to use with Scala / Groovy.
Release Notes: This release is a fresh start in many areas of jOOQ, addressing issues which have been requested by users for a long time.
Release Notes: For those of you who might not want to move to the new release 2.0 yet, there are still some bugfixes available in the 1.x branch.
Release Notes: This is a maintenance release for the 1.x branch. Developments on this branch will stop after version 1.6.9. Only important bugfixes are merged to this branch. Developments for release 2.0 have started. The most important functionality in release 1.6.9 is newly-added support for JDBC batch operations. You can now batch execute several queries.
Release Notes: The main improvement in this release is the redesign of the stored procedure/function API. With 12 supported RDBMS, which all have their own idea about what is a stored procedure and what is a stored function, it has proven to be a better design to unite them in one single type, org.jooq.Routine. A routine can have a return value as well as OUT parameters. It can be embedded in SQL and used as a field or a table.
Release Notes: This release coincides with the launch of the new Web site. Hence, it ships with little additions to the deliverable itself. Apart from new convenience methods, the main addition is a Maven plugin for jooq-codegen.
Release Notes: Finally, support for another RDBMS has been added. Sybase's other important product, Sybase Adaptive Server Enterprise (or simply Sybase ASE), is now officially supported by jOOQ. Apart from this, there were important improvements with the recently-added INSERT .. RETURNING clause, as well as some fixes related to DECIMAL/NUMERIC data types.
Release Notes: This release finally adds a loader for CSV data to jOOQ. You can now load CSV data using a simple fluent API, configuring error handling, duplicate behaviour and transaction handling, and various CSV parameters. This release also changes the way generated keys are retrieved after INSERTs. Instead of (potentially inconsistently) running SELECT MAX(pk) immediately after the INSERT, PostgreSQL's INSERT.. RETURNING clause is used (or simulated) in a single statement.
Release Notes: This release ships with a couple of useful concepts inspired by other frameworks. #selecting into custom POJOs is possible. Results can be mapped to POJOs by convention or using JPA @Column annotations. #selecting into custom callbacks, which is already a wide-spread practice in Spring JdbcTemplates. #selecting long-running queries asynchronously, an idea inspired by the Avaje Ebean framework. Apart from these changes and some bugfixes, the internal API has been completely redesigned.
Release Notes: This is mainly a maintenance release with many bugfixes, mostly around code generation, plain SQL tables, and data types. Please note that generated source code may contain incompatible changes due to #639 (see the full release notes for details). Apart from that, project CURSOR is advancing and it is now possible to unnest arrays into tables. See the attached article for details about where jOOQ is heading with project CURSOR.