Add logging for QueryBatch similar to Loader.DoQuery #2304
Merged
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.
Fixes #2296
Added logging from
Loader.DoQuery
to QueryBatchWe might also fix this one in 5.2.
It's not exactly a regression as debug logging is not a public API. And this logging is not present for criteria
MultiCriteriaImpl
but only inMultiQueryImpl
.But I agree logging for
List()
and forFuture().List()
should be the same if possible.And this logging is missing for hql Future queries in 5.2 - so might be considered as regression.
What do you think?