db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kristian Waagan (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DERBY-4587) Add tools for improved analysis and understanding of query plans and execution statistics
Date Thu, 12 Aug 2010 18:40:16 GMT

     [ https://issues.apache.org/jira/browse/DERBY-4587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Kristian Waagan updated DERBY-4587:

    Attachment: DERBY-4587-tool-9.9-formatting.diff

Attached patch DERBY-4587-tool-9.9-formatting.diff.
Committed to trunk with revision 984902.

When preparing to add ASF license headers, I realized it would be appropriate to fix some
formatting issues first. I'm sorry for doing this so quickly, Nirmal, it may cause some merge
trouble if you have code changes in your sandbox.

Here's what I did:
 o moved class JavaDoc to after the package and import statements (directly before the class
statement). The first content of the files will be the ASF license header (for more details,
see http://www.apache.org/legal/src-headers.html).
 o replaced all tab characters with spaces. Spaces are preferred for indentation in the Derby
code base. Since the files are very fresh, and some of them mixed tabs and spaces (both within
the files and on individual lines), I decided to proceed with the conversion sooner than later.
You may have to adjust your editor settings to avoid tabs in future patches (just ask on the
dev list if unsure).
 o removed some trailing whitespace

Again, sorry for doing this so abruptly (and without involving you more).

Next up is the addition of the Apache license headers.

> 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.8-modified.diff, DERBY-4587-tool-9.8.diff,
DERBY-4587-tool-9.9-formatting.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.

View raw message