You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "C.S. Nirmal J. Fernando (JIRA)" <ji...@apache.org> on 2010/05/30 03:25:35 UTC

[jira] Issue Comment Edited: (DERBY-4587) Add tools for improved analysis and understanding of query plans and execution statistics

    [ https://issues.apache.org/jira/browse/DERBY-4587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12873355#action_12873355 ] 

C.S. Nirmal J. Fernando edited comment on DERBY-4587 at 5/29/10 9:24 PM:
-------------------------------------------------------------------------

DERBY-4587-tool-2.diff patch is created in the trunk folder, and improved readability in AccessDatabase.createXMLFragment() method.

      was (Author: nirmal):
    Patch is created in the trunk folder, and improved readability in AccessDatabase.createXMLFragment() method.
  
> 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.diff, Derby_Query_Plan_Screen_Shot.jpg, PostgreSQL license.jpg, Read_Me.txt, Source.rar
>
>
> 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.