[master] fix #1408 SQL statement is printed in exceptions despite eclipselink.logging.level.sql is OFF #1415
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.
EclipseLink can print SQL statement sent to the database and control logging by the persistence unit property eclipselink.logging.level.sql(log level).
On the otherhand, EclipseLink throws exception when failed to execute SQL statement.
According to the following document, the SQL statement be only logged for log level < CONFIG in exceptions.
https://wiki.eclipse.org/EclipseLink/Examples/JPA/Logging#Log_Level_Configuration
However, when exception is thrown, SQL statement is always logged in exceptions regardless of log level.
It should be only logged for log level < CONFIG.
Signed-off-by: Ryosuke Okada [email protected]