FEATURE: NEW: QueryPlanLogger for DB2 #3144
Open
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.
This adds a queryPlanLogger for DB2. The reported query-plan is based on this script: http://use-the-index-luke.com/s/last_explained
To generate query-plans, DB2 needs do have explain tables generated with
CALL SYSPROC.SYSINSTALLOBJECTS( 'EXPLAIN', 'C' , '', ${SCHEMA})
By default, the selected schema is
CURRENT USER
. Depending on your DB2 setup, you can control this generation by an additionalqueryPlan.options
config-parameter.Examples:
ebean.db.queryPlan.options=create=false
do not create the explain tablesebean.db.queryPlan.options=create=true;schema=SYSTOOLS
create the explain tables in the SYSTOOLS schema