[
https://issues.apache.org/jira/browse/DERBY-5198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kim Haase updated DERBY-5198:
-----------------------------
Attachment: DERBY-5198.zip
DERBY-5198.stat
DERBY-5198.diff
Thanks very much, Bryan! I'm attaching DERBY-5198.diff, DERBY-5198.stat, and
DERBY-5198.zip, with a proposed patch modifying the following:
M src/ref/rrefsysxplain_sort_props.dita
M src/ref/rrefsysxplain_scan_props.dita
M src/ref/rrefsysxplain_resultsets.dita
M src/ref/rrefsysxplain_resultset_timings.dita
M src/ref/rrefsysxplain_statements.dita
With the OP_IDENTIFIER row in rrefsysxplain_resultsets.dita, I found that the
list of types is not easy to find (it is only in the Derby source code in
java/engine/org/apache/derby/impl/sql/execute/xplain/XPLAINUtil.java, as far as
I can tell), and it is also pretty long -- I'm guessing it's all the strings
with an OP_ prefix, 39 in all. But since the output is likely to be fairly
self-explanatory I don't think we need to list them.
With the OP_DETAILS row in the same topic, I left off the part about the
"Halloween" problem, which seemed like more detail than necessary -- but I can
put it back if you think it would be helpful.
Thanks for your feedback!
> XPLAIN table documentation needs some cleanup
> ---------------------------------------------
>
> Key: DERBY-5198
> URL: https://issues.apache.org/jira/browse/DERBY-5198
> Project: Derby
> Issue Type: Bug
> Components: Documentation
> Affects Versions: 10.7.1.1
> Reporter: Kim Haase
> Assignee: Kim Haase
> Priority: Minor
> Attachments: DERBY-5198.diff, DERBY-5198.stat, DERBY-5198.zip
>
>
> While working on DERBY-5184 (table cleanup), I noticed that in some of the
> XPLAIN style tables topics there remain some questions that were not answered
> by reviewers and that managed to make it into the final documentation. These
> should be fixed separately from DERBY-5184, which focuses on formatting
> rather than substantive questions.
> I'll list the problems in a comment.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
