db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kim Haase (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-4065) Provide documentation for XPLAIN style statistics processing
Date Mon, 23 Feb 2009 18:52:02 GMT

    [ https://issues.apache.org/jira/browse/DERBY-4065?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12676013#action_12676013

Kim Haase commented on DERBY-4065:

The docs look great, Bryan -- the topics and organization make perfect sense. I won't offer
any detail nits till you are past the rough-draft stage. It looks as if some implementation
details may still be in flux.

It might be helpful, in the introductory conceptual topic in the Tuning Guide, to mention
why the feature is called XPLAIN instead of EXPLAIN -- there should be a way to summarize
Felix's explanation from DERBY-2487 briefly. It's a question users are likely to ask. (You
did, I think!)

> Provide documentation for XPLAIN style statistics processing
> ------------------------------------------------------------
>                 Key: DERBY-4065
>                 URL: https://issues.apache.org/jira/browse/DERBY-4065
>             Project: Derby
>          Issue Type: Sub-task
>          Components: Documentation
>            Reporter: Bryan Pendleton
>            Assignee: Bryan Pendleton
>            Priority: Minor
>         Attachments: ctun_xplain_mode.html, ctun_xplain_tables.html, earlyDraftDocs.diff,
earlyDraftDocs.diff, earlyDraftDocs.diff, rrefresetxplaintablesproc.html, rrefsetxplainmodeproc.html,
rrefsetxplainstyleproc.html, rrefsyscsgetxplainmode.html, rrefsyscsgetxplainstyle.html, rrefsysxplain_resultset_timings.html,
rrefsysxplain_resultsets.html, rrefsysxplain_resultsets.html, rrefsysxplain_scan_props.html,
rrefsysxplain_scan_props.html, rrefsysxplain_sort_props.html, rrefsysxplain_statement_timings.html,
rrefsysxplain_statements.html, rrefsysxplain_statements.html
> This sub-task of DERBY-2487 is for tracking the documentation of the new feature. I think
> it will be a little bit simpler to track the documentation changes in a separate issue.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message