You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-commits@db.apache.org by ch...@apache.org on 2011/04/20 19:24:35 UTC
svn commit: r1095463 - in /db/derby/docs/trunk/src/ref:
rrefsysxplain_resultset_timings.dita rrefsysxplain_resultsets.dita
rrefsysxplain_scan_props.dita rrefsysxplain_sort_props.dita
rrefsysxplain_statements.dita
Author: chaase3
Date: Wed Apr 20 17:24:35 2011
New Revision: 1095463
URL: http://svn.apache.org/viewvc?rev=1095463&view=rev
Log:
DERBY-5198 XPLAIN table documentation needs some cleanup
Modified 5 Reference Manual topics.
Patches: DERBY-5198.diff
Modified:
db/derby/docs/trunk/src/ref/rrefsysxplain_resultset_timings.dita
db/derby/docs/trunk/src/ref/rrefsysxplain_resultsets.dita
db/derby/docs/trunk/src/ref/rrefsysxplain_scan_props.dita
db/derby/docs/trunk/src/ref/rrefsysxplain_sort_props.dita
db/derby/docs/trunk/src/ref/rrefsysxplain_statements.dita
Modified: db/derby/docs/trunk/src/ref/rrefsysxplain_resultset_timings.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/ref/rrefsysxplain_resultset_timings.dita?rev=1095463&r1=1095462&r2=1095463&view=diff
==============================================================================
--- db/derby/docs/trunk/src/ref/rrefsysxplain_resultset_timings.dita (original)
+++ db/derby/docs/trunk/src/ref/rrefsysxplain_resultset_timings.dita Wed Apr 20 17:24:35 2011
@@ -160,9 +160,9 @@ rows in this result set.</entry>
<entry colname="4">true</entry>
<entry colname="5">For result sets which involve a materialization of
a temporary intermediate result set, this value is the time it took to
- create the materialized result set, in milliseconds. I think this
+ create the materialized result set, in milliseconds. This materialization
may occur with hash joins where the number of rows in the intermediate
-result is too large to hold in memory?</entry>
+result is too large to hold in memory.</entry>
</row>
<row>
<entry colname="1">TEMP_CONG_FETCH_TIME</entry>
Modified: db/derby/docs/trunk/src/ref/rrefsysxplain_resultsets.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/ref/rrefsysxplain_resultsets.dita?rev=1095463&r1=1095462&r2=1095463&view=diff
==============================================================================
--- db/derby/docs/trunk/src/ref/rrefsysxplain_resultsets.dita (original)
+++ db/derby/docs/trunk/src/ref/rrefsysxplain_resultsets.dita Wed Apr 20 17:24:35 2011
@@ -86,8 +86,7 @@ colnum="5" colwidth="29*"/>
<entry colname="4">false</entry>
<entry colname="5">A code indicating what type of result set these statistics
are for.
- Common result set types include: TABLESCAN, INDEXSCAN, PROJECTION, etc.
-Should I try to list all the result set types here?</entry>
+ Common result set types include TABLESCAN, INDEXSCAN, and PROJECTION.</entry>
</row>
<row>
<entry colname="1">OP_DETAILS</entry>
@@ -190,9 +189,8 @@ rows which were inserted, updated, or de
<entry colname="5">The column is only non-null for INSERT, UPDATE, and
DELETE result sets. For those result sets, this column holds 'Y' if the
INSERT/UPDATE/DELETE is being performed using deferred change semantics,
- and holds 'N' otherwise. I think that deferred change semantics are used
- when there is self-referencing going on, and we must avoid the
- "Halloween" problem of processing the rows multiple times.
+ and holds 'N' otherwise. Deferred change semantics are used
+ when self-referencing is taking place.
</entry>
</row>
<row>
Modified: db/derby/docs/trunk/src/ref/rrefsysxplain_scan_props.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/ref/rrefsysxplain_scan_props.dita?rev=1095463&r1=1095462&r2=1095463&view=diff
==============================================================================
--- db/derby/docs/trunk/src/ref/rrefsysxplain_scan_props.dita (original)
+++ db/derby/docs/trunk/src/ref/rrefsysxplain_scan_props.dita Wed Apr 20 17:24:35 2011
@@ -181,10 +181,8 @@ scan which were found to be rows that we
<entry colname="2">INTEGER</entry>
<entry colname="3">10</entry>
<entry colname="4">true</entry>
-<entry colname="5">I think this is the number of pages fetched at a time
- when the scan is retrieving pages from disk? I expected this to be 16
- when doing a TABLESCAN, and 1 when doing an INDEXSCAN, but I've also seen
-it be 16 for INDEXSCAN?</entry>
+<entry colname="5">The number of pages fetched at a time
+ when the scan is retrieving pages from disk.</entry>
</row>
<row>
<entry colname="1">START_POSITION</entry>
Modified: db/derby/docs/trunk/src/ref/rrefsysxplain_sort_props.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/ref/rrefsysxplain_sort_props.dita?rev=1095463&r1=1095462&r2=1095463&view=diff
==============================================================================
--- db/derby/docs/trunk/src/ref/rrefsysxplain_sort_props.dita (original)
+++ db/derby/docs/trunk/src/ref/rrefsysxplain_sort_props.dita Wed Apr 20 17:24:35 2011
@@ -77,7 +77,7 @@ which required this sort to be performed
<entry colname="4">true</entry>
<entry colname="5">A code indicating the type of sort that was performed.
The code values include 'IN' for an internal sort, and 'EX' for an
- external sort. I think that an internal sort is one which was entirely
+ external sort. An internal sort is one which was entirely
performed in-memory and did not overflow to any temporary files, while an
external sort used one or more external files.</entry>
</row>
Modified: db/derby/docs/trunk/src/ref/rrefsysxplain_statements.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/ref/rrefsysxplain_statements.dita?rev=1095463&r1=1095462&r2=1095463&view=diff
==============================================================================
--- db/derby/docs/trunk/src/ref/rrefsysxplain_statements.dita (original)
+++ db/derby/docs/trunk/src/ref/rrefsysxplain_statements.dita Wed Apr 20 17:24:35 2011
@@ -73,9 +73,8 @@ colnum="5" colwidth="29*"/>
<entry colname="3">128</entry>
<entry colname="4">true</entry>
<entry colname="5">The name of the associated query or statement. This value
- is NULL if the user did not assign a name. I'm not sure how the
- user assigns a name to a statement, perhaps by
- calling Statement.setCursorName()?</entry>
+ is NULL if the user did not assign a name (by calling
+ <i>java.sql.Statement.setCursorName()</i>).</entry>
</row>
<row>
<entry colname="1">STMT_TYPE</entry>