[
https://issues.apache.org/jira/browse/DERBY-4587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
C.S. Nirmal J. Fernando updated DERBY-4587:
-------------------------------------------
Attachment: DERBY-4587-tool-6.diff
DERBY-4587-tool-test1.diff
Hi All,
I've created a test only to check the generation of XML files not to test the
correctness of XML values,
inside
"org.apache.derbyTesting.functionTests.tests.lang.XplainStatisticsTest.java",
you can find them in DERBY-4587-tool-test1.diff attached.
While creating the tests I found an important check for the zero columns
returned
in the sysxplain_resultsets for DDL statements is needed. DERBY-4587-tool-6.diff
included that modification as well.
Your comments are mostly welcome.
Thanks.
> 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: C.S. Nirmal J. Fernando
> Attachments: Derby Query Plan Screen Shot 2.jpg,
> DERBY-4587-tool-2.diff, DERBY-4587-tool-3.diff, DERBY-4587-tool-4.diff,
> DERBY-4587-tool-5.diff, DERBY-4587-tool-6.diff, DERBY-4587-tool-test1.diff,
> DERBY-4587-tool.diff, Derby_Query_Plan_Screen_Shot.jpg, PostgreSQL
> license.jpg, Read_Me.txt, screenshot-1.jpg, screenshot-2.jpg,
> screenshot-3.jpg, Simple HTML View (Pure XSL).jpg, Source.rar, test.xml,
> test4.xsl, vanilla_html.xsl, xml_doc_screenshot.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.
