JOOQ vs. Criteria API

901 views
Skip to first unread message

elect...@gmail.com

unread,
Dec 19, 2013, 1:37:46 PM12/19/13
to jooq...@googlegroups.com
Hi,

I'd like to know if there is an article or a forum thread about JOOQ vs.Criteria API (with generated metamodels)?

What is the main differences between both? What are the advantages of JOOQ?

Thanks!

Lukas Eder

unread,
Dec 20, 2013, 2:05:21 AM12/20/13
to jooq...@googlegroups.com
Hello,

2013/12/19 <elect...@gmail.com>

Hi,

I'd like to know if there is an article or a forum thread about JOOQ vs.Criteria API (with generated metamodels)? 
 
What is the main differences between both? What are the advantages of JOOQ?

The simplest answer is:

- jOOQ is typesafe SQL
- Criteria API is typesafe JPQL

From there on, you can start comparing the expressive power and usefulness of both SQL and JPQL. In other words, before comparing the above APIs, you should really think about a SQL vs. ORM/JPA-based architecture.

Being the jOOQ vendor, we believe that JPA / JPQL (and thus Criteria API) will not be able to follow suit with the expressivity of the SQL standard and of various dialects. Our views are documented in various places:

- Comparing jOOQ with LINQ, JPA, JDBC: http://www.jooq.org/doc/3.2/manual/preface/
- Comparing jOOQ with JDBC, JPA: http://www.jooq.org/why-jOOQ.pdf
- Comparing jOOQ with Hibernate: http://www.hibernate-alternative.com/
- Comparing JPA with the SQL standards: http://blog.jooq.org/2013/11/13/popular-orms-dont-do-sql/

Another point of view has been recently expressed by Vlad Mihalcea:


Cheers
Lukas

elect...@gmail.com

unread,
Dec 20, 2013, 5:13:25 AM12/20/13
to jooq...@googlegroups.com
Reply all
Reply to author
Forward
0 new messages