[
https://issues.apache.org/jira/browse/DERBY-4587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12850645#action_12850645
]
C.S. Nirmal J. Fernando commented on DERBY-4587:
------------------------------------------------
Hi Bryan,
Ya, even I expected a positive answer.
Displaying in a browser sounds interesting. We can create a XSLT style sheet
document separately as it templates the graphical query plan.
XSLT Style Sheet: I think we should first recognize the all possible instances
that can be occur in a query such as table_name, sort, hash-join etc. Next we
should write the template, as it iteratively looks for the instance occurred at
that particular step and displays the image + details (execution time, resource
usage), for all the steps that were followed when executing the query. Here
image and details can be obtained through the XML file emitted by the query
plan.
Raw XML Document: I think this XML document should contain a predefined set of
tags for all possible instances of a query as mentioned above and each tag
(Child) should contain sub-children which will describe the image + details.
And this will create at the run time in order of the execution procedure.
Next we should link Raw XML document and the XSL style sheet. This step is
fairly easy, we just need to provide the reference to the XSL style sheet
inside the XML document.
After that XSLT compliant browser will transform XML document generated by
query plan in to a XHTML page, which will show the graphical query plan +
details.
Like to get your comments on this.
> Add tools for improved analysis and understanding of query plans and
> execution statistics
> -----------------------------------------------------------------------------------------
>
> Key: DERBY-4587
> URL: https://issues.apache.org/jira/browse/DERBY-4587
> Project: Derby
> Issue Type: Improvement
> Components: SQL, Tools
> Reporter: Bryan Pendleton
> Assignee: Bryan Pendleton
> Attachments: PostgreSQL license.jpg
>
>
> I think it would be great to see some work in the area of tools for helping
> with the analysis of complex query execution. Quite frequently, users of
> Derby have trouble comprehending (a) how their query is being translated
> into a query plan by the optimizer, and (b) what the execution-time resource
> usage of the various parts of the query is.
> There are low-level features in Derby which capture this information and
> record it, such as logQueryPlan, and the XPLAIN tables, but there is a lot
> of opportunity for designing higher-level tools which can process the query
> plan and execution statistics information and present it in a more
> comprehensible fashion.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
