[ ANNOUNCEMENT ] jOOQ 3.13.3 patch release with minor improvements and bug fixes

25 views
Skip to first unread message

Lukas Eder

unread,
Jul 17, 2020, 8:01:24 AM7/17/20
to jOOQ User Group
Version 3.13.3 - July 17, 2020
================================================================================

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


Features and Improvements
-------------------------
#10222 - Support parsing CHECK constraints without parentheses
#10265 - Support \s in the code generation config's indentation configuration
#10392 - Implement TableOptions equals() and hashCode()

Bug Fixes
---------
#10173 - Wrong Javadoc: There are also DSLContext.fetchSingle() methods that return null
#10185 - Bad record type returned for selectFrom(T) when T contains LEFT SEMI JOIN or LEFT ANTI JOIN
#10208 - NullPointerException when calling Meta.apply() on an H2 database with views
#10209 - DataDefinitionException: Table can only have one identity when using Meta.apply() on PostgreSQL
#10224 - AUTO_INCREMENT columns fail to parse if they are preceded by a column with DEFAULT
#10255 - Derby date time arithmetic uses unsupported sql_tsi_milli_second
#10257 - HSQLDB cannot handle negative DAY intervals when using expression syntax
#10261 - EnumConverter doesn't work when fromType is Kotlin Int
#10270 - Settings.renderQuotedNames does not work with Routine
#10273 - NPE in Interpreter when foreign key references table from other schema that does not exist
#10302 - Columns are aliased by default to their own name, when using SQL Server parse dialect
#10314 - Javadoc of SQLDataType.INTERVAL is incorrect
#10316 - CreateSequenceFlagsStep javadoc maxvalue refers to minvalue
#10319 - Long source code workaround allocates substrings twice
#10320 - ALTER TABLE .. ADD UNIQUE INDEX syntax cannot be parsed
#10324 - join(...).onKey(TableField) doesn't work with aliased tables
#10332 - Unknown columns in code generator queries for Firebird 2.5
#10337 - jooq-meta.xsd shouldn't require table_type
#10342 - ImmutablePOJOMapperWithParameterNames throws InaccessibleObjectException on module path
#10346 - JoinTable.join(...).onKey() does not work
#10347 - NON_BIND_VARIABLE_SUFFIXES should only be used in PostgreSQL dialect
#10351 - Document Kotlin meta data usage by the DefaultRecordMapper in Javadoc
#10352 - Excluded schema is still included in code generation of foreign keys in PostgreSQL
#10357 - Loader API onDuplicateKeyIgnore() doesn't work when primary key is an identity
#10371 - General exception error has occurred in the optimizer in Informix code generation, when generating only one schema and <includeSystemIndexes/> is turned on
#10393 - XMLGenerator should quote source code from views, check constraints, and default expressions in generated output
#10395 - <sources/> and <sourcesOnViews/> are not implemented in XMLGenerator
#10414 - maven-deploy.sh and maven-install.sh should use #!/bin/bash

Lukas Eder

unread,
Jul 20, 2020, 6:08:32 AM7/20/20
to jOOQ User Group
An important regression has been detected between 3.13.2 and 3.13.3:
https://github.com/jOOQ/jOOQ/issues/10425 (ImmutablePOJOMapperWithParameterNames no longer injects default values for unmapped primitive arguments).

No workaround exists yet. If you're using ImmutablePOJOMapperWithParameterNames (e.g. with @ConstructorProperties on mapped POJOs), please wait with the upgrade. A fix should hopefully be published this week.

Thanks,
Lukas
Reply all
Reply to author
Forward
0 new messages