The main improvement of this release is the re-design 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.
This means, you will need to re-generate your database schema, when upgrading to jOOQ 1.6.8. After re-generation, you'll need to fix your client code. These are the package changes: - [generated.package].procedures > [generated.package].routines - [generated.package].functions > [generated.package].routines - [generated.package].Procedures > [generated.package].Routines - [generated.package].Functions > [generated.package].Routines Oracle generated packages are not re-located. With these improvements, using stored procedures and functions becomes even more reliable, especially when cursor types are involved. Read more about the rationale behind this change: http://lukaseder.wordpress.com/2011/10/17/what-are-procedures-and-functions-after-all/ Apart from that, important improvements have been made in the area of plain SQL tables. Also, consider a demo integration of jOOQ with Google Cloud SQL: http://lukaseder.wordpress.com/2011/10/22/jooq-and-google-cloud-sql-example/ Check out the full release notes here: http://www.jooq.org/notes.php
