Tweet of the Day
Our followers, users and customers are shouting their love for jOOQ to the world. Here are:
Ben Hood who is constantly discovering new useful features in jOOQ.
Antoine Comte who is skipping MyBatis to jump directly to jOOQ (in French)
Both guys are absolutely right, of course!
jOOQ 3.3 was an exciting release. But now we’re heading towards the next upgrade, and it’s not going to be any less exciting. Here are the top interesting topics that might be in scope for jOOQ 3.4:
- IBM Informix support for the jOOQ Professional Edition.
- Typesafe DDL support for the most common statement types.
- Transaction management. We’ve been discussing this a lot of times and we would love to provide some jOOQ-style Java-8 ready default behaviour. As always, with plenty of options to override the defaults.
- TABLE types and TABLE-valued functions in all databases. This is already very useful in jOOQ 3.3’s SQL Server integration.
- SQL 2 jOOQ improvements and a UI to transform SQL to jOOQ code.
As you can see, plenty of goodies coming up! Missing a feature? Write us!
We’re thrilled to have spotted yet another great article by Vlad Mihalcea, who is discovering the merits of using jOOQ for interaction with stored procedures and functions. If you’re doing a deep SQL integration with your favourite database of choice, stored procedures are a very useful tool in your tool chain. Unfortunately, neither JDBC nor JPA offer any convenience in that area, in a way as jOOQ does.Read the full article here.
Besides, we’re very happy to have found that our friends at RebelLabs are excited with our blog posts, such that they have featured a guest post of ours on their blog. RebelLabs have a tremendous amount of great content from many writers, so we’re very honoured to present our guest post to you.
One of the most important topics when writing SQL is performance, as the database is the bottleneck in most applications. And surprisingly, 60% of all SQL developers will fail this little test performed by the Use The Index, Luke guys.
This blog post is a must-read for all juniors and seniors alike. You never stop learning about correct SQL indexing.
Boolean types have been introduced only late in the SQL standard, namely inSQL:1999. Even today, not all databases natively support BOOLEAN or BIT types. Most importantly, we can still wait for them in Oracle for a while.
What does this mean for Java developers striving for a maximum compatibility through JDBC? Read our findings in this blog post here.
February has been a bit quiet as we were preparing for the jOOQ 3.3 release, but soon you’ll get another chance at hearing about jOOQ or SQL in general in any of these upcoming events:
- March 20, 2014: JUGS Zürich (German, about SQL)
- April 4, 2014: JUG Saxony Day in Dresden (German, about jOOQ)
- April 7, 2014: VSUG in Vienna (English, about jOOQ in Scala!)
- May 14 – 16, 2014: Geecon in Kraków (English, about jOOQ)
With our new SQL-talk, we’ll no longer just spread some jOOQ love, but also some SQL love in general. We believe that SQL deserves more presence in today’s software engineering talks, and who would be better to talk about SQL than us? Are you interested in hosting this talk at your company? Contact us!
Stay informed about 2014 events on www.jooq.org/news.