-
Notifications
You must be signed in to change notification settings - Fork 41.2k
JooqExceptionTranslator passes null exception to jOOQ when SQLException cannot be translated #25717
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
This was referenced Mar 17, 2021
This was referenced Mar 18, 2021
Closed
Merged
Bump spring-boot-starter-parent from 2.4.2 to 2.4.4
checkmarx-ltd/checkmarx-spring-boot-java-sdk#108
Merged
Closed
sgrimm
added a commit
to terraware/terraware-server
that referenced
this issue
Dec 15, 2021
While developing the search code, it was annoying to keep running into spring-projects/spring-boot#25717 which caused database error messages to not show up in the logs. The bug was fixed in the patch version of Spring Boot just after the one we were using.
kallen07
pushed a commit
to terraware/terraware-server
that referenced
this issue
Dec 15, 2021
While developing the search code, it was annoying to keep running into spring-projects/spring-boot#25717 which caused database error messages to not show up in the logs. The bug was fixed in the patch version of Spring Boot just after the one we were using.
humaolin
pushed a commit
to humaolin/spring-boot
that referenced
this issue
May 7, 2022
humaolin
pushed a commit
to humaolin/spring-boot
that referenced
this issue
May 7, 2022
… as well Closes spring-projectsgh-25717 (cherry picked from commit 613b05d)
humaolin
pushed a commit
to humaolin/spring-boot
that referenced
this issue
May 7, 2022
… as well Closes spring-projectsgh-25717 (cherry picked from commit 613b05d)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Rather than calling
ExecuteContext(RuntimeException)
withnull
, we shouldn't call jOOQ at all. This will lead to throwing the original SQLException wrapped in a jOOQDataAccessException
, just as if theJooqExceptionTranslator
hadn't been configured.See #25493 for further details.
The text was updated successfully, but these errors were encountered: