jOOQ 3.21

Apply the Java 21 prompt first. These rules cover jOOQ 3.21 on Java 21, with the Open Source Edition as the baseline, and were checked against 3.21.7. Apply rules for commercial policies and hidden, readonly, or redacted columns only when the deployed edition supports them.

Version scope and generated code

• Align jooq, jooq-meta, jooq-codegen, generator plugins, and extension modules to the same release and compatible edition/JDK distribution; configure the SQLDialect for the deployed database.
• Generate from a trusted schema with a separate metadata account, and restrict the application's database role to required runtime operations. Review generator configuration, forced types, custom strategies, converters, bindings, and generated output after migrations; code-generation includes/excludes do not restrict database access at runtime.
• Check resolved dependencies as well as jOOQ's version: application BOMs and overrides must not undo 3.21.7's Jackson and Spring security updates. Assess advisories for the optional modules and dependency versions actually installed.

SQL construction and escape hatches

• Use generated fields, typed DSL comparisons, and DSL.val() for values; retain the default StatementType.PREPARED_STATEMENT for ordinary application queries.
• Restrict @PlainSQL APIs, including DSL.sql(), string overloads of condition, field, table, query, resultQuery, and fluent where/from, to reviewed constant templates. Pass values through ? bindings or DSL.val() query parts in {0} templates; never interpolate input into