| Detecting good candidates for join fetch hints [message #1728073] |
Wed, 30 March 2016 18:30 |
 Dave Brosius
Messages: 35
Registered: July 2009 |
Member |
|
|
Greetings,
Assume you have a eclipselink application that has hundreds of named queries, and assume that various of these are used with join fetch query hints throughout the product. However it is highly likely that there are plenty of other locations where a join fetch hint would be useful, but is not present.
You could certainly visually inspect every query use, but that is a very tedious process, and only happens at one point in time.
I'd like to be able to somehow add some tracing/logging code that automatically catches say an over abundance of secondary queries to fulfill the joins of a primary query, where a proper join fetch hint isn't specified, where the result would be the main query in question and some sort of stack frame showing how it was called. Is this possible? How would this be done.
[Updated on: Wed, 30 March 2016 18:31] Report message to a moderator |
|
|
Powered by
FUDForum. Page generated in 0.03374 seconds
] 
Search
Help
Register
Login
Home
