Hi Community, With the help of Espen, we have succeeded in releasing version 1.5.3 with lots of additional stored procedure support and bugfixes. Check out the release notes for details: https://sourceforge.net/projects/jooq/files/Release/RELEASENOTES.txt
Extended support for stored procedures, advanced datatypes and other vendor-specific RDBMS constructs are the primary goals and features of jOOQ, apart from its fluent DSL that helps for fast creation of SQL in Java. The feedback I had in my dzone article about stored procedures, as well as on stackoverflow and other media is promising. We're on the right track. Check out the dzone article here: http://java.dzone.com/articles/2011-great-year-stored This means that our primary goals for release 1.5.4 will be: - More stored procedure / package / UDT integration - Support for ARRAY types - Support for CURSOR types and similar constructs - Support for at least one more database Take part in the database discussion thread here: http://stackoverflow.com/questions/4685107/what-other-rdbms-should-my-open-source-java-persistence-library-support The change of paradigm is manifesting more and more. When I started creating jOOQ, I was thinking that I was about to create YAORM - Yet Another OR-mapper. Very untrue as can be seen today. See for example Timo Westkämper's appreciated comments on the jOOQ user group: http://groups.google.com/group/jooq-user/browse_thread/thread/bbde77f2e01ea8e8 In fact, jOOQ really embraces the active record pattern, staying close to the "relational" and to the database. With this switch of paradigm, long-term goals will be to interface with JPA/Hibernate and possibly other ORMs in a different way where the OR-mapper can be put "on top" of jOOQ. We'll see what the future brings. Let's get to work for release 1.5.4! :-) Cheers Lukas
