Go to file
Lukas Eder 054c7f6224 [jOOQ/jOOQ#644] Support POJO type hierarchy
This first draft will omit calls to super.xyz() in various POJO type hierarchy levels, assuming the super type implementation (and its attributes) can be ignored completely given that all methods are overridden. If this assumption isn't true, we can still fix things, but I prefer not to complicate *everything* unless it's necessary.

Some implementations are still wrong as they should downcast known supertypes to their subtypes, e.g. constructors when accepting <interfaces/> types.
2024-09-05 12:03:33 +02:00
.github/ISSUE_TEMPLATE Remove OS from issue templates 2024-03-12 09:19:22 +01:00
jOOQ [jOOQ/jOOQ#17181] Add native support for DISTINCT ON in DuckDB 2024-09-04 16:06:08 +02:00
jOOQ-beans-extensions [#16988] Correctly name Apache-2.0 everywhere 2024-07-29 12:53:09 +02:00
jOOQ-checker [#16988] Correctly name Apache-2.0 everywhere 2024-07-29 13:00:52 +02:00
jOOQ-codegen [jOOQ/jOOQ#644] Support POJO type hierarchy 2024-09-05 12:03:33 +02:00
jOOQ-codegen-gradle [jOOQ/jOOQ#15936] Implicit path correlation produces correlation 2024-08-20 15:32:41 +02:00
jOOQ-codegen-maven [#16988] Correctly name Apache-2.0 everywhere 2024-07-29 13:00:52 +02:00
jOOQ-jackson-extensions [#16988] Correctly name Apache-2.0 everywhere 2024-07-29 13:00:52 +02:00
jOOQ-jpa-extensions [#16988] Correctly name Apache-2.0 everywhere 2024-07-29 13:00:52 +02:00
jOOQ-kotlin [#16988] Correctly name Apache-2.0 everywhere 2024-07-29 12:53:09 +02:00
jOOQ-kotlin-coroutines [#16988] Correctly name Apache-2.0 everywhere 2024-07-29 12:53:09 +02:00
jOOQ-meta [jOOQ/jOOQ#12180] Add a jOOQ-scala-3.5 extension library 2024-08-29 14:55:35 +02:00
jOOQ-meta-extensions [#16988] Correctly name Apache-2.0 everywhere 2024-07-29 13:00:52 +02:00
jOOQ-meta-extensions-hibernate [#16988] Correctly name Apache-2.0 everywhere 2024-07-29 13:00:52 +02:00
jOOQ-meta-extensions-liquibase [#16988] Correctly name Apache-2.0 everywhere 2024-07-29 13:00:52 +02:00
jOOQ-meta-kotlin [#16988] Correctly name Apache-2.0 everywhere 2024-07-29 12:53:09 +02:00
jOOQ-migrations [#16988] Correctly name Apache-2.0 everywhere 2024-07-29 13:00:52 +02:00
jOOQ-migrations-maven [#16988] Correctly name Apache-2.0 everywhere 2024-07-29 13:00:52 +02:00
jOOQ-postgres-extensions [#16988] Correctly name Apache-2.0 everywhere 2024-07-29 13:00:52 +02:00
jOOQ-scala_3.5 [jOOQ/jOOQ#12180] Add a jOOQ-scala-3.5 extension library 2024-08-29 14:55:35 +02:00
jOOQ-xtend [jOOQ/jOOQ#15936] Implicit path correlation produces correlation 2024-08-20 15:32:41 +02:00
.gitignore [jOOQ/jOOQ#11700] Add a jOOQ-r2dbc module (ignore for now) 2021-03-23 09:16:39 +01:00
.travis.yml
CONTRIBUTING.md Update CONTRIBUTING.md 2023-11-16 11:59:04 +01:00
LICENSE [#16988] Correctly name Apache-2.0 everywhere 2024-07-29 12:53:09 +02:00
pom.xml [jOOQ/jOOQ#17150] Update Scala dependencies to 2.12.19 and 2.13.14 2024-08-29 17:06:55 +02:00
README.md Add policies to README 2024-01-15 13:18:28 +01:00
SECURITY.md Create SECURITY.md 2022-04-19 10:53:35 +02:00

jOOQ

jOOQ is an internal DSL and source code generator, modelling the SQL language as a type safe Java API to help you write better SQL.

Its main features include:

Secondary features include:

Examples

Typesafe, embedded SQL

jOOQ's main feature is typesafe, embedded SQL, allowing for IDE auto completion of SQL syntax...

image

... as well as of schema meta data:

image

This allows for preventing errors of various types, including typos of identifiers:

image

Or data type mismatches:

image

The examples are from the code generation blog post.

A more powerful example using nested collections

For many more examples, please have a look at the demo. A key example showing jOOQ's various strengths is from the MULTISET operator announcement blog post:

Given these target DTOs:

record Actor(String firstName, String lastName) {}
record Film(
  String title,
  List<Actor> actors,
  List<String> categories
) {}

You can now write the following query to fetch films, their nested actors and their nested categorise in a single, type safe query:

List<Film> result =
dsl.select(
      FILM.TITLE,
      multiset(
        select(
          FILM.actor().FIRST_NAME, 
          FILM.actor().LAST_NAME)
        .from(FILM.actor())
      ).as("actors").convertFrom(r -> r.map(mapping(Actor::new))),
      multiset(
        select(FILM.category().NAME)
        .from(FILM.category())
      ).as("categories").convertFrom(r -> r.map(Record1::value1))
   )
   .from(FILM)
   .orderBy(FILM.TITLE)
   .fetch(mapping(Film::new));

The query is completely type safe. Change a column type, name, or the target DTO, and it will stop compiling! Trust only your own eyes:

multiset

And here you see the nested result in action from the logs:

execute

How does it work? Look at this annotated example:

List<Film> result =
dsl.select(
      FILM.TITLE,

      // MULTISET is a standard SQL operator that allows for nesting collections
      // directly in SQL. It is either
      // - supported natively
      // - emulated using SQL/JSON or SQL/XML
      multiset(

        // Implicit path based joins allow for simpler navigation of foreign
        // key relationships.
        select(
          FILM.actor().FIRST_NAME, 
          FILM.actor().LAST_NAME)

        // Implicit correlation to outer queries allows for avoiding repetitive
        // writing of predicates.
        .from(FILM.actor())

      // Ad-hoc conversion allows for mapping structural Record2<String, String>
      // types to your custom DTO using constructor references
      ).as("actors").convertFrom(r -> r.map(mapping(Actor::new))),
      multiset(
        select(FILM.category().NAME)
        .from(FILM.category())
      ).as("categories").convertFrom(r -> r.map(Record1::value1))
   )
   .from(FILM)
   .orderBy(FILM.TITLE)
   .fetch(mapping(Film::new));

The generated SQL query might look like this, in PostgreSQL:

select
  film.title,
  (
    select coalesce(
      jsonb_agg(jsonb_build_object(
        'first_name', t.first_name,
        'last_name', t.last_name
      )),
      jsonb_build_array()
    )
    from (
      select
        alias_78509018.first_name, 
        alias_78509018.last_name
      from (
        film_actor
          join actor as alias_78509018
            on film_actor.actor_id = alias_78509018.actor_id
        )
      where film_actor.film_id = film.film_id
    ) as t
  ) as actors,
  (
    select coalesce(
      jsonb_agg(jsonb_build_object('name', t.name)),
      jsonb_build_array()
    )
    from (
      select alias_130639425.name
      from (
        film_category
          join category as alias_130639425
            on film_category.category_id = alias_130639425.category_id
        )
      where film_category.film_id = film.film_id
    ) as t
  ) as categories
from film
order by film.title

This particular example is explained more in detail in the MULTISET operator announcement blog post. For many more examples, please have a look at the demo.