# jooq-in-use Published articles for jooq-in-use. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Simplifying ANTI JOIN with jOOQ Syntax DevFeed: [Simplifying ANTI JOIN with jOOQ Syntax]() Original publisher: [Read original article]() Author: lukaseder Published: 2026-05-07T11:26:46Z Content type: tutorial Language: en Sources: [jOOQ]() Topics: [SQL](), [rdbms](), [clickhouse](), [databricks]() Tags: [anti-join](), [clickhouse](), [databricks](), [join-paths](), [jooq](), [jooq-in-use](), [sql](), [sql-syntax]() ### AI overview The article explains how to express an anti join more concisely with jOOQ. It shows that jOOQ can render native anti-join syntax for supported RDBMSs such as ClickHouse and Databricks, translate it for other systems, and use implicit correlated path joins introduced in jOOQ 3.19. ### Source excerpt ANTI JOIN is a very useful operator from relational algebra. Regrettably, only few dialects support it in terms of SQL syntax, as we've written earlier. In jOOQ, you can write it as follows: If your RDBMS supports this natively (e.g. ClickHouse, Databricks), then it is rendered as such. Otherwise, jOOQ will translate this to: But ... Continue reading Simplifying ANTI JOIN with jOOQ Syntax -> ## Managing Sensitive Data in jOOQ 3.21+ Logs DevFeed: [Managing Sensitive Data in jOOQ 3.21+ Logs]() Original publisher: [Read original article]() Author: lukaseder Published: 2026-03-27T12:45:19Z Content type: tutorial Language: en Sources: [jOOQ]() Topics: [Logging](), [sensitive data](), [Security](), [configuration](), [Code]() Tags: [configuration](), [csv](), [debug-logging](), [jooq](), [jooq-in-use](), [json](), [logging](), [logs](), [maven](), [redacted-columns](), [security](), [sensitive-data](), [xml]() ### AI overview This article explains how jOOQ debug logging can expose query bind values and fetched records in application logs, creating security concerns in production. It describes a code-generation configuration available in commercial jOOQ distributions to mask exported data, including text, HTML, and optionally CSV, JSON, or XML output. ### Source excerpt One of jOOQ's most popular feature is the out-of-the-box debug logging experience. jOOQ developers find this feature very useful when developing their applications. Assuming you run a jOOQ query and configure your logger to print DEBUG log output: When this query is executed, your log output might contain something like this: Executing query : select ... Continue reading Managing Sensitive Data in jOOQ 3.21+ Logs -> ## A Hidden Benefit of Implicit Joins: Join Elimination DevFeed: [A Hidden Benefit of Implicit Joins: Join Elimination]() Original publisher: [Read original article]() Author: lukaseder Published: 2024-01-10T14:19:00Z Content type: article Language: en Sources: [jOOQ]() Topics: [SQL](), [Databases](), [rdbms]() Tags: [implicit-joins](), [implicit-path-join](), [java](), [join-elimination](), [jooq](), [jooq-3-19](), [jooq-in-use](), [many-to-many-joins](), [optimisation](), [path-joins](), [sql](), [to-many-joins]() ### AI overview This article explains how jOOQ 3.19 can eliminate unnecessary tables from implicit path joins when no columns from those tables are referenced. Primary and foreign keys preserve equivalence, while referenced columns cause the table to remain in the join tree. The behavior applies to implicit path joins and depends on a flag that is disabled by default. ### Source excerpt One of jOOQ's key features so far has always been to render pretty much exactly the SQL that users expect, without any surprises - unless some emulation is required to make a query work, of course. This means that while join elimination is a powerful feature of many RDBMS, it isn't part of jOOQ's feature ... Continue reading A Hidden Benefit of Implicit Joins: Join Elimination -> ## Workaround for MySQL's "can't specify target table for update in FROM clause" Error DevFeed: [Workaround for MySQL's "can't specify target table for update in FROM clause" Error]() Original publisher: [Read original article]() Author: lukaseder Published: 2023-12-20T14:20:29Z Content type: tutorial Language: en Sources: [jOOQ]() Topics: [MySQL](), [SQL](), [bug](), [rdbms]() Tags: [bug](), [for-update](), [from-clause](), [jooq-in-use](), [mariadb](), [mysql](), [rdbms](), [sql](), [table](), [target-table](), [update]() ### AI overview The article explains MySQL error 1093, which occurs when an UPDATE statement references its target table in a FROM clause. It presents a jOOQ transformation as a workaround and notes that similar workarounds appear in the MySQL documentation. ### Source excerpt In MySQL, you cannot do this: The UPDATE statement will raise an error as follows: SQL Error [1093] [HY000]: You can't specify target table 't' for update in FROM clause People have considered this to be a bug in MySQL for ages, as most other RDBMS can do this without any issues, including MySQL clones: ... Continue reading Workaround for MySQL's "can't specify target table for update in FROM clause" Error -> ## jOOQ DAOs, CRUD Access, and the N+1 Query Problem DevFeed: [jOOQ DAOs, CRUD Access, and the N+1 Query Problem]() Original publisher: [Read original article]() Author: lukaseder Published: 2023-12-06T13:41:52Z Content type: opinion Language: en Sources: [jOOQ]() Topics: [CRUD](), [SQL](), [Domain-driven design (DDD)](), [Transactions](), [account]() Tags: [account](), [api](), [crud](), [dao](), [data](), [ddd](), [developers](), [join](), [jooq](), [jooq-in-use](), [optimisation](), [repository](), [sql](), [transactions]() ### AI overview This opinion article examines jOOQ's DAO API and the tendency to use DAOs or repositories for quick CRUD access. It argues that this approach can obscure query design and lead to inefficient patterns such as N+1 queries, while showing how explicit SQL and bulk operations can improve query structure and performance. ### Source excerpt jOOQ's DAO API is one of jOOQ's most controversial features. When it was first implemented, it was implemented merely: There's a strong hint about the third bullet given how popular Spring Data's repository "pattern" is. A lot of developers just want to quickly fetch and store data, without giving individual queries much thought. A fun ... Continue reading To DAO or not to DAO -> ## How to Generate Package Private Code with jOOQ's Code Generator DevFeed: [How to Generate Package Private Code with jOOQ's Code Generator]() Original publisher: [Read original article]() Author: lukaseder Published: 2023-06-28T15:54:18Z Content type: tutorial Language: en Sources: [jOOQ]() Topics: [Code](), [Java](), [Code generation](), [configuration](), [Java 9]() Tags: [code](), [code-generation](), [code-generator](), [compilation](), [configuration](), [how-to](), [java](), [java-9](), [jooq](), [jooq-code-generator](), [jooq-in-use](), [modularity](), [package-private](), [visibility](), [visibility-modifier]() ### AI overview This tutorial explains Java package-private visibility and shows how to configure jOOQ's code generator to generate package-private types. The approach can help keep generated jOOQ implementation details from leaking into client code. ### Source excerpt Java's package private visibility is an underrated feature. When you omit any visibility modifier in Java, then the default (for most objects) is package private, i.e. the object is visible only to types in the same package: In fact, a compilation unit (the .java file) can contain multiple such classes. You don't have to create ... Continue reading How to Generate Package Private Code with jOOQ's Code Generator -> ## How to Pass a Table Valued Parameter to a T-SQL Function with jOOQ DevFeed: [How to Pass a Table Valued Parameter to a T-SQL Function with jOOQ]() Original publisher: [Read original article]() Author: lukaseder Published: 2023-04-25T12:16:30Z Content type: tutorial Language: en Sources: [jOOQ]() Topics: [sql-server](), [SQL](), [Java](), [Code]() Tags: [code](), [code-generation](), [code-generator](), [how-to](), [java](), [jdbc](), [jooq](), [jooq-in-use](), [sql-server](), [t-sql](), [table-valued-function](), [table-valued-parameter]() ### AI overview This tutorial explains how to pass a Microsoft T-SQL table-valued parameter to a function using jOOQ. It covers native T-SQL and JDBC usage, then shows how jOOQ's code generator produces Java types and methods for calling the function and accessing its result rows. ### Source excerpt Microsoft T-SQL supports a language feature called table-valued parameter (TVP), which is a parameter of a table type that can be passed to a stored procedure or function. For example, you may write: This function takes a table-valued parameter (TVP), and produces a result set containing the cross product of the parameter table with itself. ... Continue reading How to Pass a Table Valued Parameter to a T-SQL Function with jOOQ -> ## How to use jOOQ's Converters with UNION Operations DevFeed: [How to use jOOQ's Converters with UNION Operations]() Original publisher: [Read original article]() Author: lukaseder Published: 2023-03-02T11:18:17Z Content type: tutorial Language: en Sources: [jOOQ]() Topics: [SQL](), [Databases]() Tags: [ad-hoc-converter](), [converter](), [how-to](), [jdbc](), [jooq](), [jooq-in-use](), [lambda](), [multiset](), [r2dbc](), [rdbms](), [sql](), [union]() ### AI overview This tutorial explains how jOOQ ad-hoc converters behave with UNION operations. Because conversion occurs on the client after JDBC retrieval, it does not affect server-side UNION processing, and jOOQ applies the result-fetching row type from the first subquery. The article recommends applying client-side conversions consistently across subqueries or moving the conversion to the server when appropriate. ### Source excerpt jOOQ 3.15 introduced the concept of an ad-hoc converter, a converter that is applied "ad-hoc" to a single query. It uses the same underlying mechanisms as any ordinary Converter that is attached to generated code for use in every query. An example of such an ad-hoc converter is this: While there are other ways to ... Continue reading How to use jOOQ's Converters with UNION Operations -> ## How to Write a Derived Table in jOOQ DevFeed: [How to Write a Derived Table in jOOQ]() Original publisher: [Read original article]() Author: lukaseder Published: 2023-02-24T09:18:48Z Content type: tutorial Language: en Sources: [jOOQ]() Topics: [SQL](), [Java](), [Databases]() Tags: [cte](), [derived-table](), [how-to](), [jooq](), [jooq-in-use](), [sql](), [type-safety]() ### AI overview This tutorial explains how to write derived tables and common table expressions in jOOQ. It notes that derived-table columns are not fully type-safe in Java, and shows that simplifying an SQL query can sometimes eliminate the derived table and allow greater use of generated code. ### Source excerpt One of the more frequent questions about jOOQ is how to write a derived table (or a CTE). The jOOQ manual shows a simple example of a derived table: In SQL: In jOOQ: And that's pretty much it. The question usually arises from the fact that there's a surprising lack of type safety when working ... Continue reading How to Write a Derived Table in jOOQ -> ## Why You Should Execute jOOQ Queries With jOOQ DevFeed: [Why You Should Execute jOOQ Queries With jOOQ]() Original publisher: [Read original article]() Author: lukaseder Published: 2023-01-18T11:46:25Z Content type: opinion Language: en Sources: [jOOQ]() Topics: [SQL](), [Java](), [Databases](), [Compiler]() Tags: [code-generation](), [crud](), [csv](), [execution](), [export](), [identity](), [import](), [java](), [jdbc](), [jooq](), [jooq-in-use](), [jpa](), [json](), [mapping](), [multiset](), [nested-collections](), [nested-records](), [orm](), [r2dbc](), [sql](), [stored-procedures](), [type-safety](), [udt](), [updatablerecord](), [user-defined-types](), [xml]() ### AI overview The article argues that queries built with jOOQ should generally also be executed with jOOQ. It explains that jOOQ preserves type safety and structured result mapping during execution, whereas extracting SQL and bind values for JDBC-level execution loses compiler knowledge of the result set. It acknowledges limited use cases for executing jOOQ-generated SQL elsewhere, such as a small number of dynamic queries in an otherwise JPA-based application. ### Source excerpt Previously on this blog, I've written a post explaining why you should use jOOQ's code generator, despite the possibility of using jOOQ without it. In a similar fashion, as I've answered numerous jOOQ questions on Stack Overflow, where someone used jOOQ to build a query, but then executed it elsewhere, including on: jOOQ itself isn't ... Continue reading Why You Should Execute jOOQ Queries With jOOQ -> ## jOOQ's R2DBC LoggingConnection to log all SQL statements DevFeed: [jOOQ's R2DBC LoggingConnection to log all SQL statements]() Original publisher: [Read original article]() Author: lukaseder Published: 2023-01-17T10:12:05Z Content type: article Language: en Sources: [jOOQ]() Topics: [SQL](), [reactive](), [Code]() Tags: [code](), [dependency](), [hibernate](), [jdbc](), [jdbctemplate](), [jooq](), [jooq-in-use](), [logging](), [native](), [r2dbc](), [reactive](), [sql]() ### AI overview The article introduces jOOQ's LoggingConnection for R2DBC clients, which logs reactive SQL queries. It notes that the utility is available in jOOQ versions 3.18.0, 3.17.7, and 3.16.13, and that standalone code is available on GitHub. ### Source excerpt jOOQ already has a LoggingConnection (see also the manual), which acts as a JDBC proxy Connection to log all SQL statements that are executed by any JDBC client (including Hibernate, MyBatis, JdbcTemplate, native JDBC, etc.). Starting from jOOQ 3.18.0, 3.17.7, and 3.16.13, a LoggingConnection is now also available for R2DBC clients to log all reactive ... Continue reading jOOQ's R2DBC LoggingConnection to log all SQL statements -> ## When to Use jOOQ and When to Use Native SQL DevFeed: [When to Use jOOQ and When to Use Native SQL]() Original publisher: [Read original article]() Author: lukaseder Published: 2022-12-08T13:53:02Z Content type: comparison Language: en Sources: [jOOQ]() Topics: [SQL](), [Databases](), [rdbms](), [Test-driven development](), [Testcontainers]() Tags: [cons](), [examples](), [jdbc](), [jdbctemplate](), [jdbi](), [jooq](), [jooq-in-use](), [native-sql](), [plain-jdbc](), [plain-sql-templating](), [rdbms](), [sql](), [sql-json](), [stored-procedures](), [tdd](), [testcontainers]() ### AI overview This comparison explains when to use the jOOQ API and when to use native SQL for complex queries. It describes jOOQ's advantages for dynamic SQL, multiple database dialects, type safety, data mapping, stored procedures, security, exports, and diagnostics, while noting usability drawbacks for large static queries with many CTEs or derived tables. ### Source excerpt A frequently encountered doubt people have when using jOOQ is to decide when a "complex" query should be written using jOOQ API vs. when it should be implemented using native SQL. The jOOQ manual is full of side by side examples of the same query, e.g. Using jOOQ: Using native SQL: In the native SQL ... Continue reading When to Use jOOQ and When to Use Native SQL -> ## Calling Procedures with Default Parameters using JDBC or jOOQ DevFeed: [Calling Procedures with Default Parameters using JDBC or jOOQ]() Original publisher: [Read original article]() Author: lukaseder Published: 2022-10-21T14:35:39Z Content type: tutorial Language: en Sources: [jOOQ]() Topics: [Code](), [Reason](), [SQL](), [Oracle Database](), [PostgreSQL]() Tags: [db2](), [default-parameters](), [java](), [jdbc](), [jooq](), [jooq-in-use](), [oracle](), [pl-pgsql](), [pl-sql](), [postgresql](), [sql-server](), [stored-functions](), [stored-procedures](), [syntax]() ### AI overview This tutorial explains how to call stored procedures with default parameters using JDBC or jOOQ. It shows how directly instantiating a procedure call allows Java code to omit parameters that have database-side defaults, and notes that syntax varies across supported relational database systems. ### Source excerpt Using jOOQ's code generator to call stored procedures is a popular reason to use jOOQ. For example, when you have a procedure like the following Oracle PL/SQL procedure: jOOQ will generate code for you to call very simply, like this: This will execute the following, taking care of binding all IN and OUT parameters for ... Continue reading Calling Procedures with Default Parameters using JDBC or jOOQ -> ## Using jOOQ's Implicit Join From Within the JOIN .. ON Clause DevFeed: [Using jOOQ's Implicit Join From Within the JOIN .. ON Clause]() Original publisher: [Read original article]() Author: lukaseder Published: 2022-09-13T07:29:59Z Content type: tutorial Language: en Sources: [jOOQ]() Topics: [SQL](), [PostgreSQL]() Tags: [dictionary-views](), [how-to](), [implicit-join](), [information-schema](), [jooq](), [jooq-3-17](), [jooq-in-use](), [pg-catalog](), [postgresql](), [sql](), [technical]() ### AI overview This tutorial explains how to use jOOQ's type-safe implicit JOINs from within an explicit JOIN ... ON clause. It uses PostgreSQL dictionary views and related tables as an example, and describes how jOOQ generates SQL while preserving operator precedence. ### Source excerpt Starting with jOOQ 3.11, type safe implicit JOIN have been made available, and they've been enhanced to be supported also in DML statements in jOOQ 3.17. Today, I'd like to focus on a somewhat weird but really powerful use-case for implicit JOIN, when joining additional tables from within an explicit JOIN's ON clause. The use ... Continue reading Using jOOQ's Implicit Join From Within the JOIN .. ON Clause -> ## A Brief Overview over the Most Common jOOQ Types DevFeed: [A Brief Overview over the Most Common jOOQ Types]() Original publisher: [Read original article]() Author: lukaseder Published: 2022-09-06T12:30:37Z Content type: tutorial Language: en Sources: [jOOQ]() Topics: [SQL](), [API](), [Databases](), [Structured-data]() Tags: [api](), [api-design](), [cheat-sheet](), [configuration](), [context](), [dependency-injection](), [dsl](), [jdbc](), [jooq](), [jooq-3-17](), [jooq-in-use](), [logging](), [overview](), [queryparts](), [r2dbc](), [sql](), [syntax](), [type-system](), [types]() ### AI overview This tutorial provides a cheat sheet of the most important types in the jOOQ API, covering configuration, scopes, settings, and DSL APIs. It notes that jOOQ 3.17 includes more than 160 settings and explains how several type groups support query construction, execution, lifecycle management, and dependency injection. ### Source excerpt For new users working with jOOQ for the first time, the number of types in the jOOQ API can be overwhelming. The SQL language doesn't have many such "visible" types, although if you think about SQL the way jOOQ does, then they're there just the same, but hidden from users via an English style syntax. ... Continue reading A Brief Overview over the Most Common jOOQ Types -> ## The Second Best Way to Fetch a Spring Data JPA DTO Projection DevFeed: [The Second Best Way to Fetch a Spring Data JPA DTO Projection]() Original publisher: [Read original article]() Author: lukaseder Published: 2022-08-30T14:48:44Z Content type: tutorial Language: en Sources: [jOOQ]() Topics: [Code](), [Spring Boot]() Tags: [code](), [dto-projection](), [jooq](), [jooq-in-use](), [nested-collections](), [repositories](), [spring-boot](), [spring-data-jpa]() ### AI overview The article presents jOOQ as a second way to implement a Spring Data JPA DTO projection. It shows value-constructor and aggregate-function approaches, emphasizing type-safe record conversion and reduced infrastructure code. ### Source excerpt I've just stumbled upon this great post by Vlad Mihalcea, titled The Best Way to Fetch a Spring Data JPA DTO Projection. It got some nice traction on reddit, too. This is such a nice use-case and apt solution, I wanted to quickly show the second best way of doing the same, with jOOQ this ... Continue reading The Second Best Way to Fetch a Spring Data JPA DTO Projection -> ## Cannot resolve symbol 'VERSION\_3\_17' in jOOQ generated code DevFeed: [Cannot resolve symbol 'VERSION\_3\_17' in jOOQ generated code]() Original publisher: [Read original article]() Author: lukaseder Published: 2022-08-30T06:56:20Z Content type: tutorial Language: en Sources: [jOOQ]() Topics: [Code](), [Compiler](), [Code generation](), [Gradle](), [Maven]() Tags: [code-generation](), [compilation](), [compilation-error](), [compiler](), [errors](), [gradle](), [java](), [jooq](), [jooq-in-use](), [location](), [maven]() ### AI overview This article explains that a VERSION_3_17 compilation error in jOOQ-generated code is caused by a mismatch between the runtime library and code generation library. The runtime version must be at least as new as the code generation version; matching both versions is recommended. ### Source excerpt Starting with jOOQ 3.16 and #12601, there may be a compilation error with a message like this in your jOOQ generated code: [ERROR] .../DefaultCatalog.java:[53,73] cannot find symbol[ERROR] symbol: variable VERSION_3_17[ERROR] location: class org.jooq.Constants Typically, this error is mixed with other compilation errors in generated code. Its purpose is to help troubleshoot these other compilation errors. ... Continue reading Cannot resolve symbol 'VERSION_3_17' in jOOQ generated code -> ## A Condition is a Field DevFeed: [A Condition is a Field]() Original publisher: [Read original article]() Author: lukaseder Published: 2022-08-24T09:09:11Z Content type: tutorial Language: en Sources: [jOOQ]() Topics: [SQL](), [Databases]() Tags: [boolean](), [boolean-type](), [condition](), [data-type](), [jooq](), [jooq-3-17](), [jooq-in-use](), [logic](), [oracle](), [postgresql](), [predicate](), [sql](), [three-valued-logic]() ### AI overview The article explains that, starting with jOOQ 3.17, the Condition type extends Field, allowing conditions to be projected directly and used wherever boolean value expressions are accepted. It describes compatibility differences between PostgreSQL and Oracle and jOOQ's emulation of the feature while preserving three-valued logic. ### Source excerpt Starting with jOOQ 3.17, the Condition type extends the Field type. Because, that's what the SQL standard thinks it is, in sorts: The exact definition contains intermediate rules, but you get the idea. A (which is a Condition in jOOQ) can be used wherever a can be used, which again can ... Continue reading A Condition is a Field -> ## How to Integration Test Stored Procedures with jOOQ DevFeed: [How to Integration Test Stored Procedures with jOOQ]() Original publisher: [Read original article]() Author: lukaseder Published: 2022-08-22T12:36:00Z Content type: tutorial Language: en Sources: [jOOQ]() Topics: [Testing](), [Database](), [Testcontainers](), [Java](), [PostgreSQL]() Tags: [code](), [code-generation](), [database](), [gradle](), [how-to](), [integration-test](), [integration-testing](), [java](), [jooq](), [jooq-in-use](), [junit](), [maven](), [stored-procedures](), [testcontainers](), [unit-test]() ### AI overview This tutorial explains how to integration-test database stored procedures and functions with Java, jOOQ, Testcontainers, and JUnit. It shows how to run PostgreSQL in Testcontainers, generate jOOQ classes for stored procedures, and reuse Java test infrastructure instead of manually binding to procedures through JDBC. ### Source excerpt When you write stored procedures and functions in your database, you want to ensure their correctness, just like with your Java code. In Java, this is done with unit tests, typically with JUnit. For example, if you have the following code in Java: Then, you might write a test like this: But how do we ... Continue reading How to Integration Test Stored Procedures with jOOQ -> ## Using H2 as a Test Database Product with jOOQ DevFeed: [Using H2 as a Test Database Product with jOOQ]() Original publisher: [Read original article]() Author: lukaseder Published: 2022-08-19T07:25:43Z Content type: tutorial Language: en Sources: [jOOQ]() Topics: [in-memory database](), [Testing](), [Java](), [SQL](), [sql-server]() Tags: [compatibility-mode](), [database](), [h2](), [in-memory-database](), [integration-testing](), [java](), [jooq](), [jooq-in-use](), [sql](), [sql-server](), [testcontainers](), [testing](), [vendor-agnosticity]() ### AI overview This article explains the trade-offs of using H2 as a test database for Java applications with jOOQ. It shows why SQL that works on H2 may require syntax changes on SQL Server, describes H2 compatibility modes, and notes that jOOQ generates SQL for H2's native dialect rather than its compatibility modes. ### Source excerpt The H2 database is an immensely popular in-memory database product mostly used by Java developers for testing. If you check out the DB-Engines ranking, it ranks 50th, which is quite impressive, as this rank outperforms products like: CockroachDB Ignite Single Store (previously MemSQL) Interbase (which was forked as Firebird) Ingres (which is a predecessor to ... Continue reading Using H2 as a Test Database Product with jOOQ -> ## The Best Way to Call Stored Procedures from Java: With jOOQ DevFeed: [The Best Way to Call Stored Procedures from Java: With jOOQ]() Original publisher: [Read original article]() Author: lukaseder Published: 2022-07-28T13:11:59Z Content type: tutorial Language: en Sources: [jOOQ]() Topics: [Code generation](), [Java](), [SQL](), [data-processing](), [Server]() Tags: [code-generation](), [code-generator](), [data-processing](), [java](), [jdbc](), [jdbc-drivers](), [jooq](), [jooq-in-use](), [oracle](), [pl-pgsql](), [pl-sql](), [postgresql](), [rdbms](), [schema](), [sql](), [stored-functions](), [stored-procedures](), [t-sql](), [udts]() ### AI overview This tutorial explains how to call stored procedures from Java using jOOQ-generated code. It contrasts JDBC calls with generated procedure stubs and convenience methods, covering parameter handling, database types, and support for procedures, functions, packages, and UDTs. ### Source excerpt jOOQ is mainly known for its powerful type safe, embedded, dynamic SQL capabilities that are made available through code generation. However, a secondary use case of code generation is to use it for stored procedures (possibly exclusively for stored procedures). Stored procedures are powerful ways of moving complex data processing logic to the server. This ... Continue reading The Best Way to Call Stored Procedures from Java: With jOOQ -> ## The Many Different Ways to Fetch Data in jOOQ DevFeed: [The Many Different Ways to Fetch Data in jOOQ]() Original publisher: [Read original article]() Author: lukaseder Published: 2022-05-19T07:29:09Z Content type: tutorial Language: en Sources: [jOOQ]() Topics: [jooq](), [Java](), [SQL]() Tags: [collections](), [collector](), [convenience](), [fetching](), [java](), [jdbc](), [joo-f6a0c60d3d07](), [jooq](), [jooq-in-use](), [optional](), [r2dbc](), [reactive-streams](), [sql](), [stream-api](), [streams]() ### AI overview This tutorial explains several ways to fetch data with jOOQ, including eager result-set fetching, external and internal iteration, single-record retrieval, optional results, and resource-managed fetching for large data sets. ### Source excerpt The jOOQ API is all about convenience, and as such, an important operation (the most important one?) like fetch() must come with convenience, too. The default way to fetch data is this: It fetches the entire result set into memory and closes the underlying JDBC resources eagerly. But what other options do we have? Iterable ... Continue reading The Many Different Ways to Fetch Data in jOOQ -> ## How to Typesafely Map a Nested SQL Collection into a Nested Java Map with jOOQ DevFeed: [How to Typesafely Map a Nested SQL Collection into a Nested Java Map with jOOQ]() Original publisher: [Read original article]() Author: lukaseder Published: 2022-05-09T10:06:51Z Content type: tutorial Language: en Sources: [jOOQ]() Topics: [Java](), [SQL](), [Databases](), [data](), [Structured-data]() Tags: [collections](), [data](), [data-structures](), [how-to](), [java](), [jooq](), [jooq-in-use](), [map](), [mapping](), [multiset](), [nested-collections](), [nested-maps](), [nested-records](), [sql](), [stack-overflow](), [typesafety]() ### AI overview This tutorial shows how to use jOOQ 3.15's ad-hoc conversion API and nested collection features to map a nested SQL collection into a type-safe nested Java Map. It uses the Sakila database example and explains how collectors preserve insertion order. ### Source excerpt A really cool, recent question on Stack Overflow was about how to map a nested collection into a Java Map with jOOQ. In the past, I've blogged about the powerful MULTISET operator many times, which allows for nesting collections in jOOQ. This time, instead of nesting data into a List, why not nest it in ... Continue reading How to Typesafely Map a Nested SQL Collection into a Nested Java Map with jOOQ ->