Version 3.19.29 - December 5, 2025

This is a 3.19 patch release with minor improvements and bug fixes

Features and Improvements

#19396 - Add Settings.interpreterWithMetaLookups

Bug Fixes

#19363 - SQL Server JSON_ARRAY() emulation produces StackOverflowError with 1000+ arguments #19371 - Bad performance when reading / writing PGInterval values to pgjdbc #19375 - Inconsistent Support annotations between DerivedColumnsList::as and DerivedColumnList[N]::as #19387 - DELETE .. RETURNING with RAW type doesn't work in Oracle #19391 - Compilation error in generated Record POJO constructors when table uses a table type reference in PostgreSQL #19399 - Error when generating code for SQLite table containing both UNIQUE and FOREIGN KEY, when referenced table has no UNIQUE key #19403 - DefaultOtherBinding may produce bind variable marker despite Settings.statementType being set to STATIC_STATEMENT for some dialects #19408 - Generated AbstractRoutine setters aren't all affected by the <fluentSetters/> code generation flag #19412 - BatchSingle executed with R2DBC doesn't attach batched query to Configuration #19421 - Code generator does not maintain DataTypeDefinition::generationOption when applying forced type #19440 - Refactor internal Multiset::accept0 logic to avoid redundancy between JSON and JSONB handling #19443 - Overridable generateRecord(definition, writer) and generateUDTRecord(definition, writer) are not used in JavaGenerator #19447 - DefaultRenderContext.checkForceInline() does not work for R2DBC connections #19450 - KotlinGenerator does not produce deepEquals/deepHashCode calls for jooq-postgres-extensions array types #19455 - Update PostgreSQL parameter count limit to 65535 #19460 - DSLContext::batchMerge's Support documentation should match that of UpdatableRecord::merge #19467 - Wrong SQL rendered for ALTER TABLE .. RENAME CONSTRAINT in SQL Server #19470 - Wrong SQL rendered for ALTER TABLE IF EXISTS .. RENAME CONSTRAINT in SQL Server #19475 - Wrong support documented on RENAME CONSTRAINT clause for Db2