set the loggerName of the locally generated LogRecords (#1167) #1188
Conversation
In ConnectionFactoryImpl.log function locally generates the logRecord but doesn't set the loggerName of the current Logger, as a result the log ignores the class or package level logging configuration
rhavermans
added a commit
to bolcom/pgjdbc
that referenced
this pull request
Jul 13, 2018
In ConnectionFactoryImpl.log function locally generates the logRecord but doesn't set the loggerName of the current Logger, as a result the log ignores the class or package level logging configuration fixes pgjdbc#1167
rhavermans
added a commit
to bolcom/pgjdbc
that referenced
this pull request
Jul 13, 2018
In ConnectionFactoryImpl.log function locally generates the logRecord but doesn't set the loggerName of the current Logger, as a result the log ignores the class or package level logging configuration fixes pgjdbc#1167
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.
In ConnectionFactoryImpl.log function locally generates the logRecord
but doesn't set the loggerName of the current Logger, as a result
the log ignores the class or package level logging configuration