[
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-7.diff
Hi,
In this patch DERBY-4587-tool-7.diff, I modified the code as per comments of
Bryan.
1) I used indexOf() instead of contains(), in AccessDatabase class.
2) I added the entry for new tool in "\tools\jar\tools.properties" and now the
new tool
is successfully added to derbytools.jar.
3) --When I run XplainStatisticsTest, I get AccessDenied exceptions
--trying to write the XML files.
Bryan, I've no idea why this happened, in my environment it ran successfully.
---I'm not sure exactly where the test is
---trying to write these test files, but it seems the location is not
acceptable to
---the security policy that is getting used by the tests.
The xml files are created in the same directory, where you have executed
the test file.
4) I've included the statement executed and attached a screen shot
"basic_html-2".
Appreciate your comments.
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: basic_html-2.jpg, 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-7.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.
