Wrong jOOQ exception translator with empty db name #44954
Closed
Conversation
This file contains hidden or 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
Signed-off-by: Dennis Melzer <[email protected]>
Signed-off-by: Dennis Melzer <[email protected]>
spring-projects-issues
added
the
status: waiting-for-triage
snicoll
added
type: bug
snicoll
changed the title
snicoll
pushed a commit
that referenced
this pull request
Apr 17, 2025
This commit updates jOOQ's DefaultExceptionTranslatorExecuteListener to fallback on Spring Framework's default if no dbName is available. See gh-44954 Signed-off-by: Dennis Melzer <[email protected]>
snicoll
added a commit
that referenced
this pull request
Apr 17, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Fix default exception translator for jooq translator without special db name handling
fix #44869