jOOQ Object Oriented Querying, commonly known as jOOQ, is a light database-mapping software library in Java that implements the active record pattern. Its purpose is to be both relational and object oriented by providing a domain-specific language to construct queries from classes generated from a database schema.^{[citation needed]}

jOOQ claims that SQL should come first in any database integration. Thus, it does not introduce a new textual query language, but rather allows for constructing plain SQL from jOOQ objects and code generated from a database schema. jOOQ uses JDBC to call the underlying SQL queries. ^{[citation needed]}

While it provides abstraction on top of JDBC, jOOQ does not have as much functionality and complexity as standard object–relational mapping libraries such as EclipseLink or Hibernate.^{[citation needed]}

jOOQ's closeness to SQL has advantages over typical object–relational mapping libraries. ^{[citation needed]} SQL has many features that cannot be used in an object oriented programming paradigm; this set of differences is referred to as the object–relational impedance mismatch. By being close to SQL, jOOQ helps to prevent syntax errors and type mapping problems. ^{[citation needed]} Also, variable binding is taken care of. It is also possible in jOOQ to create very complex queries, that involve aliasing, unions, nested selects and complex joins. jOOQ also supports database-specific features, such as UDTs, enum types, stored procedures and native functions. ^{[citation needed]}

A nested query selecting from an aliased table

  -- Select authors with books that are sold out
  SELECT * FROM AUTHOR a
        WHERE EXISTS (SELECT 1
                   FROM BOOK
                  WHERE BOOK.STATUS = 'SOLD OUT'
                    AND BOOK.AUTHOR_ID = a.ID);

And its equivalent in jOOQ DSL:

  // Use the aliased table in the select statement
  create.selectFrom(table("AUTHOR").as("a"))
        .where(exists(selectOne()
                     .from(table("BOOK"))
                     .where(field("BOOK.STATUS").equal(field("BOOK_STATUS.SOLD_OUT")))
                     .and(field("BOOK.AUTHOR_ID").equal(field("a.ID")))));

Or more simply, using code generation from the database metadata to generate constants:

  // Use the aliased table in the select statement
  final Author a = AUTHOR.as("a");

  create.selectFrom(a)
        .where(exists(selectOne()
                     .from(BOOK)
                     .where(BOOK.STATUS.equal(BOOK_STATUS.SOLD_OUT))
                     .and(BOOK.AUTHOR_ID.equal(a.ID))));

• Apache Calcite
• List of object–relational mapping software
• SQL/OLB

• jOOQ Home
• Using Spring Boot with jOOQ
• JSR-341
• JaQu Archived 2021-05-05 at the Wayback Machine
• Linq4j
• Quaere
• QueryDSL

v t e Java (software platform)
Platforms	JVM Java ME (Micro) Java SE (Standard) Jakarta EE (Enterprise) Java Card Android SDK GraalVM
Oracle technologies	Squawk Java Development Kit OpenJDK Java virtual machine JavaFX Maxine VM
Platform technologies	Applets Servlets MIDlets JSP JSF Web Start (JNLP) Pack200 Modules
Major third-party technologies	Blackdown Eclipse GNU Classpath GWT Harmony Hibernate IcedTea Jazelle Spring Struts TopLink WildFly
History	Java version history Java Community Process Sun Microsystems Free Java implementations
JVM languages	Java BeanShell Clojure Groovy JRuby Jython Kotlin Processing Rhino Scala Oxygene
Community	Conferences JavaOne Devoxx Organizations Apache Software Foundation Eclipse Foundation Java Community Process Oracle Corporation Sun Microsystems, Sun Microsystems Laboratories People James Gosling Arthur van Hoff Urs Hölzle Patrick Naughton
Category   Computer programming portal