[
https://issues.apache.org/jira/browse/DERBY-2487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12676158#action_12676158
]
Bryan Pendleton commented on DERBY-2487:
----------------------------------------
I need to investigate how this should work in an upgrade scenario. Is there
already
code which runs during upgrade which would detect that these system tables do
not yet exist, and would create them? Also, is there anything special needed so
that,
if the system tables do not yet exist, then the feature is smart enough to not
allow
itself to be turned on until the system tables are created (e.g., in "soft"
upgrade)?
> Enhance Derby with EXPLAIN Functionality
> ----------------------------------------
>
> Key: DERBY-2487
> URL: https://issues.apache.org/jira/browse/DERBY-2487
> Project: Derby
> Issue Type: New Feature
> Components: SQL
> Affects Versions: 10.2.2.0
> Reporter: Felix Beyer
> Assignee: Bryan Pendleton
> Priority: Minor
> Attachments: Derby physical XPLAIN schema.png,
> incorporateTrunkChanges.diff, RSProtocolNew.pdf, rts.xls, small logical
> xplain schema.pdf, startRegressionTest.diff, startRegressionTest.diff,
> updateRegressionTests.diff, updateRegressionTests.diff, usage.txt,
> xplain_patch_v1.txt, xplainClasses.pdf
>
>
> This enhancement extends Derby with EXPLAIN functions. Users want to have
> more feedback than they`re getting with the current RuntimeStatistics
> facility. This extension is based on the
> RuntimeStatistics/ResultSetStatistics functions / classes.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
