Upgrade jOOQ 3.19.16 -> 3.19.17 #1504
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Suggested commit message: |
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
3.19.16->3.19.17Release Notes
jOOQ/jOOQ (jOOQ)
v3.19.17: 3.19.17Version 3.19.17 - January 8, 2025
This is a 3.19 patch release with minor improvements and bug fixes
Features and Improvements
#17809 - Parse and ignore ALTER SEQUENCE .. OWNED BY syntax
Bug Fixes
#17766 - Javadoc typo on MergeNotMatchedStep.whenNotMatchedThenInsert
#17772 - Parser doesn't correctly parse MERGE with multiple WHEN MATCHED clauses if the last WHEN MATCHED clause doesn't have any AND clause
#17779 - Missing trigger meta data in code generation output for Oracle INSTEAD OF triggers on views
#17788 - NullPointerException in SchemaMapping due to race condition in SchemaMapping cache
#17792 - Regression when enabling <jpaAnnotation> for NOT NULL DEFAULT columns, which should continue to be marked as @Column(nullable = true)
#17795 - Exception in MetaImpl when encountering string literal default expressions in MariaDB 10.1
#17799 - T-SQL dialects should generate LTRIM(string, characters) (and RTRIM) instead of TRIM(LEADING characters FROM string) for better overall compatibility
#17812 - Parser doesn't support qualified identifiers in DROP TYPE statement
#17824 - SQLDialect.AURORA_POSTGRES should cast JSONB and similar types in INSERT statements
#17829 - SQLDialect.AURORA_POSTGRES renders wrong syntax for pgplsql local variable assignments
#17833 - Specific overloads of DSL.val(X) no longer infers data type of built-in type X for null values
#17838 - Double or Float inline values should be cast to their appropriate types where the rendered literals are interpreted as NUMERIC or DECIMAL