jOOQ
jOOQ copied to clipboard
jOOQ
jOOQ is the best way to write SQL in Java
jOOQ 3.21 introduces support for `MetaImpl::getUDTs`: - https://github.com/jOOQ/jOOQ/issues/18792 So far, this doesn't include PL/SQL package types yet, which will be supported separately.
JDK 25 is the next LTS by Oracle due in September 2025: - https://www.oracle.com/java/technologies/java-se-support-roadmap.html It's still early to follow suit in jOOQ for jOOQ 3.21 or probably even 3.22, but...
### Use case I have run into a case when I have `ResultQuery`/`Cursor` and I'd like to have `ResultQuery`/`Cursor`. `B` derives nicely from `A`, I just want to encapsulate mapping...
UDT paths are a code generation only feature, currently, implemented in jOOQ 3.19: - https://github.com/jOOQ/jOOQ/issues/228 We do not yet support them in the parser: - https://github.com/jOOQ/jOOQ/issues/18748 Nor as a way...
We support defaulted parameters for functions, but we cannot reverse engineer them for all RDBMS. For example: - Db2's `SYSCAT.FUNCPARMS` doesn't contain a column to check the `DEFAULT` expression -...
The changes related to: - https://github.com/jOOQ/jOOQ/issues/19044 ... have introduced a regression in Oracle when generating code for PL/SQL package routines whose parameters have UDT defaults, for example: ```sql PROCEDURE pls_p_rdefault...
### Expected behavior When working with Kotlin inline value classes that are in the result set due to converters (i.e. map an `Int` to a UserId which wraps an `Int`)...
https://github.com/jOOQ/jOOQ/issues/2786 finally implements `NULL` handling of the `SEEK` method: ```java .orderBy(T.A.nullsFirst(), T.B.nullsFirst()) .seek(null, "X") ``` However, we do not yet support nullable expressions correctly, e.g. this doesn't work: ```java .orderBy(T.A.nullsFirst(),...
We currently create the `ExecuteContext` instance only for actual executions, e.g. to pass to `ExecuteListener` instances, but also internals. The `ExecuteContext` contains some cached instances of various other SPI and...
Historically, we only supported the JDBC types for `` in `Field`, and then a few of our own, including `UByte` or `JSON`, etc. Later on, it became clear this design...