Tweet of the Day and Webinar with Arun Gupta from Red Hat
Today, we have a very special Tweet of the Day by Oliver Hubaut who expresses what we believe is a general feeling in the industry. He says:
The more I use it, the more I'm convinced that JPA is a waste of time... except for a pet store. I miss @JavaOOQ so much!
See his Tweet here: https://twitter.com/ohubaut/status/531783784023465984
There is a lot of truth in his statement, albeit perhaps not the one he intended. Many people have misinterpreted JPA in the past, believing that it will be a full replacement for SQL. This couldn't be farther from the truth.
Gavin King, the creator of Hibernate has told us the following:
... and this is also the point we're trying to make. Join us next week on Wednesday, December 3 when we meet with Arun Gupta from Red Hat for his Webinar about JPA and jOOQ. If you have any questions that you'd like us to talk about, ask them here:
Black Friday Sale: Get 20% off any jOOQ purchase, today!
We're participating in the Black Friday sale tradition and give you an incredible 20% off your purchase of any jOOQ license that you order today, Black Friday, November 28, 2014.
Ask your manager today to treat you to a wonderful pre-christmas gift!
Don't waste time, act quickly and order jOOQ licenses right now:
jOOQ 3.5 released
If you've been following the jOOQ User Group, you've heard it already. Last Friday, we've shipped the awesome jOOQ 3.5 with loads of new features!
The new Binding SPI
The main improvement of this exciting release is the new org.jooq.Binding SPI
which can be used to fully control all aspects of a user-type's JDBC interaction.
This goes much further than the existing org.jooq.Converter SPI that can be used
to map standard JDBC types to user-types. With the new Binding SPI, virtually
*ALL* vendor-specific types can be supported now. Examples include PostgreSQL's
JSON or HSTORE types, or Oracle's DATE type - which is really incorrectly
represented via java.sql.Timestamp, which is why we have retrofitted the existing
<dateAsTimestamp/> feature to use such bindings, now.
Stored procedures are everywhere
Stored procedure support was generally improved in this release. This includes
lots of new little features and conveniences for use with PL/SQL or Transact-SQL.
For instance, jOOQ 3.5.0 now supports cross-schema references of PL/SQL OBJECT
and TABLE types, which allows for binding directly to Oracle Spatial. We've
blogged about this exciting improvement here:
And while we were at it, we've also added basic support for Oracle AQ, which
integrates very nicely with our OBJECT type support!
In Transact-SQL and MySQL, we now support fetching arbitrary numbers of Results
from stored procedures, and we've also implemented support for Firebird PSQL,
including Firebird's very interesting syntax for table-valued functions.
By the way, we support user-defined aggregate functions for a variety of
databases, including Oracle, PostgreSQL, and HSQLDB. Definitely something you
should look into!
In this release, we've finally got support for UNION, INTERSECT, and EXCEPT
right with respect to nesting such operations, as well as combining them with
ORDER BY and LIMIT .. OFFSET.
Let's talk some more DDL
We've continued to add support for DDL statements, including
We'll continue to add support for more DDL statements also in the future.
- CREATE TABLE
- CREATE TABLE AS SELECT
- CREATE VIEW and DROP VIEW
- CREATE INDEX and DROP INDEX
- CREATE SEQUENCE and DROP SEQUENCE
- DROP .. IF EXISTS
Code generation improvements
We've added support for the new XMLDatabase, a code generation configuration
that allows to read meta information from XML formats, e.g. from a standard
INFORMATION_SCHEMA.xml, or from Vertabelo's XML export format:
Future versions of jOOQ will include built-in support for a variety of XML
We've had an awesome contribution by Etienne Studer from Gradleware to help our
users integrate the jOOQ code generation with their Gradle builds.
Last but not least: Informix!
Oh, and by the way, we now also support IBM's second most popular database:
Informix. Support for this database will be included in the jOOQ Enterprise
More information can be found here:
jOOQ 3.2 End of Life
While 3.5 is out, 3.2 is now more than one year old, which means that it has reached its end of life. We'll be shipping a last patch update 3.2.7 in early December. After that, we advise all our customers and users to upgrade to a newer minor release.
Do you want to stay on the 3.2 release? No problem, contact our sales team and we'll find a solution for you.