[
https://issues.apache.org/jira/browse/DERBY-4587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12896914#action_12896914
]
C.S. Nirmal J. Fernando commented on DERBY-4587:
------------------------------------------------
Hi Kristian,
Thanks for looking into the code and give me your feedback, I find
them very useful, I'll attach a patch soon.
Please see my comments below.
a) Pardon me for not adding the license header. Thanks for
looking into that.
--- AccessDatabase
b) If it is the case I'll change to dbUrl.indexOf("://").
c) It's better if you can help me a bit on this, I'm not that familiar
of using meta data calls.
d) Whoops, I forgot to removed those automatic generated @author
tags.
e) I'll modify this.
f) Yep, it's better not to shutdown, instead we can only close the connection.
--- PlanExporter
g) I'll make it to private. Tool runs with the permissions given to
derbytools.jar.
--- TreeNode
h) I'll make it to package-private.
i) I'll make it implicit. No need to explicitly inherit.
j) Removed it.
k) I might had a reason earlier, but you're right no need of a String now.
--- CreateHTMLFile
l) I'll add this.
m) thanks for the idea.
--- CreateXMLFile
n) Actually I can't think of a way of doing that. Can you please explain a bit.
o) I think I should change it to "Apache Derby Query Explainer (DERBY-4587)". :)
p) I'm afraid not, will using the default be a problem?
Thank you very much!
> 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: AdavancedXSL-mouseover.jpg, advancedViewXSL.xsl,
> advancedViewXSL.xsl, advancedViewXSL2.xsl, advancedXSL-1.jpg,
> advancedXSL-2.jpg, advancedXSL-3.jpg, basic_html-2.2.jpg, basic_html-2.3.jpg,
> basic_html-2.jpg, basic_html-3.jpg, basic_html-4.1.jpg, basic_html-4.2.jpg,
> Derby Query Plan Screen Shot 2.jpg, DERBY-4587-javadoc_fix.diff,
> 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-b.diff,
> DERBY-4587-tool-7.diff, DERBY-4587-tool-8.diff, DERBY-4587-tool-9.1.diff,
> DERBY-4587-tool-9.2.diff, DERBY-4587-tool-9.3.diff, DERBY-4587-tool-9.4.diff,
> DERBY-4587-tool-9.5.diff, DERBY-4587-tool-9.6.diff, DERBY-4587-tool-9.7.diff,
> DERBY-4587-tool-9.7.diff, DERBY-4587-tool-9.diff, DERBY-4587-tool-test1.diff,
> DERBY-4587-tool-test2.diff, DERBY-4587-tool.diff, derby-logo.png,
> 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,
> vanilla_html.xsl, vanilla_html.xsl, vanilla_html.xsl, vanilla_html.xsl,
> xml_doc_screenshot.jpg, 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.
