Welcome to the jOOQ Tuesdays series. In this series, we’ll publish an article on the third Tuesday every other month where we interview someone we find exciting in our industry from a jOOQ perspective. This includes people who work with SQL, Java, Open Source, and a variety of other related topics. We have the pleasure … Continue reading jOOQ Tuesdays: Vlad Mihalcea Gives Deep Insight into SQL and Hibernate
Tag: jpa
Leaky Abstractions, or How to Bind Oracle DATE Correctly with Hibernate
We've recently published an article about how to bind the Oracle DATE type correctly in SQL / JDBC, and jOOQ. This article got a bit of traction on reddit with an interesting remark by Vlad Mihalcea, who is frequently blogging about Hibernate, JPA, transaction management and connection pooling on his blog. Vlad pointed out that … Continue reading Leaky Abstractions, or How to Bind Oracle DATE Correctly with Hibernate
The “Free”, “Standard”, “Open” Software Heresy
There are those people that have a strong, dogmatic belief in what they call "Free" or "Standard" or "Open" software. One of those individuals is Jimmie (let's call him Jimmie in this article) who has responded to an article about Java persistence by Marco Behler on TheServerSide. Let me cite Jimmie's response here: JPA is … Continue reading The “Free”, “Standard”, “Open” Software Heresy
QueryDSL vs. jOOQ. Feature Completeness vs. Now More Than Ever
This week, Timo Westkämper from QueryDSL has announced feature completeness on the QueryDSL user group, along with his call for contributions and increased focus on bugfixes and documentation. Timo and us, we have always been in close contact, observing each other's products. In the beginning of jOOQ in 2009, QueryDSL was ahead of us. But … Continue reading QueryDSL vs. jOOQ. Feature Completeness vs. Now More Than Ever
Popular ORMs Don’t do SQL
I'm contemplating about what has happened in the ISO / IEC SQL standard during the last 15 years. We've had quite a few new features added to our beloved SQL language. Check this out: With the ISO/IEC SQL:1999 standard, we could take advantage of grouping sets and (recursive) common table expressions. With the ISO/IEC SQL:2003 standard, we’ve … Continue reading Popular ORMs Don’t do SQL
High Complexity and Low Throughput. Reasons for Using an ORM.
I've recently stumbled upon an interesting blog post about when to use an ORM. I found it to be well-written and quite objective, specifically with respect to its model complexity and throughput diagram: The ORM or not ORM topic will probably never stop showing up on blogs. Some of them are more black and white, … Continue reading High Complexity and Low Throughput. Reasons for Using an ORM.
LINQ and Java
LINQ has been quite a successful, but also controversial addition to the .NET ecosystem. Many people are looking for a comparable solution in the Java world. To better understand what a comparable solution could be, let's have a look at the main problem that LINQ solves: Query languages are often declarative programming languages with many … Continue reading LINQ and Java
A Typesafety Comparison of SQL Access APIs
SQL is a very expressive and distinct language. It is one of the few declarative languages which are used by a broad audience in everyday work. As a declarative language, SQL allows to specify what we're expecting as output, not how this output should be produced. As a side-effect of this, ad-hoc record data types … Continue reading A Typesafety Comparison of SQL Access APIs
jOOQ’s Reason for Being
The below paragraphs were taken from the jOOQ preface from the manual. It is worth thinking about why you should (or should not) use jOOQ in a given project. Specifically, you might be choosing between jOOQ and JPA, jOOQ and Hibernate, or jOOQ and SLICK (in a Scala context). here's some guidance (slightly biased towards … Continue reading jOOQ’s Reason for Being
jOOQ makes a step forward towards JPA
With the upcoming release 1.6.4 and the implementation of #198, jOOQ will start to better integrate in "standard" J2EE architecture. While jOOQ is being developed as an alternative to JPA, it should not compete with it. This means that there are some parts in JPA which can easily co-exist with jOOQ in a J2EE application: … Continue reading jOOQ makes a step forward towards JPA