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 2010/08/12 18:29:27 UTC
svn commit: r984851 - in /db/derby/docs/trunk/src/tools: ctoolsplanexp.dita
ctoolspre11181.dita ctoolspre23947.dita ctoolsusingplanexp.dita
derbytools.ditamap rtoolsplanexpexamples.dita rtoolsplanexpxmlformat.dita
Author: chaase3
Date: Thu Aug 12 16:29:26 2010
New Revision: 984851
URL: http://svn.apache.org/viewvc?rev=984851&view=rev
Log:
DERBY-4758: Adding documentation about the PlanExporter Tool
Revisions to previous patch with style and formatting corrections, and links from introductory topics. Future changes can build on these.
Patches: derby-4758-3.diff, derby-4758-3a.diff
Added:
db/derby/docs/trunk/src/tools/rtoolsplanexpxmlformat.dita (with props)
Modified:
db/derby/docs/trunk/src/tools/ctoolsplanexp.dita
db/derby/docs/trunk/src/tools/ctoolspre11181.dita
db/derby/docs/trunk/src/tools/ctoolspre23947.dita
db/derby/docs/trunk/src/tools/ctoolsusingplanexp.dita
db/derby/docs/trunk/src/tools/derbytools.ditamap
db/derby/docs/trunk/src/tools/rtoolsplanexpexamples.dita
Modified: db/derby/docs/trunk/src/tools/ctoolsplanexp.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/tools/ctoolsplanexp.dita?rev=984851&r1=984850&r2=984851&view=diff
==============================================================================
--- db/derby/docs/trunk/src/tools/ctoolsplanexp.dita (original)
+++ db/derby/docs/trunk/src/tools/ctoolsplanexp.dita Thu Aug 12 16:29:26 2010
@@ -17,23 +17,25 @@ limitations under the License.
-->
<!DOCTYPE concept PUBLIC "-//OASIS//DTD DITA Concept//EN" "../dtd/concept.dtd">
<concept xml:lang="en-us" id="ctoolsplanexp">
-<title>PlanExporter Tool</title>
+<title>PlanExporter</title>
<prolog><metadata>
<keywords><indexterm>PlanExporter</indexterm></keywords>
</metadata>
</prolog>
<conbody>
<p>Use the <codeph>PlanExporter</codeph> tool to export query plan data for
-further analysis. The query plan data can be exported in a variety of formats.
-The base format for exported query plan data is XML. Query plan data can also
-be exported in HTML format, which helps you view graphically
-the execution plans of complex queries you have executed. By using this tool
-you can avoid querying <codeph>XPLAIN style tables</codeph> to get a
-basic idea of the query plan followed by the <codeph>Optimizer</codeph>.
-You can specify other query plan export formats by specifying an appropriate
+further analysis. The query plan data can be exported in a variety of formats:
+</p>
+<ul>
+<li>XML, the base format for exported query plan data</li>
+<li>HTML, which helps you view graphically the execution plans of complex
+queries you have executed</li>
+</ul>
+<p>By using this tool, you can avoid querying XPLAIN style tables to get a
+basic idea of the query plan followed by the optimizer.</p>
+<p>You can specify other query plan export formats by specifying an appropriate
XSL stylesheet to transform the query plan data, or you can export the
query plan data as XML, then reformat as appropriate using any external
-XML-aware tool of your choice.
-</p>
+XML-aware tool of your choice.</p>
</conbody>
</concept>
Modified: db/derby/docs/trunk/src/tools/ctoolspre11181.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/tools/ctoolspre11181.dita?rev=984851&r1=984850&r2=984851&view=diff
==============================================================================
--- db/derby/docs/trunk/src/tools/ctoolspre11181.dita (original)
+++ db/derby/docs/trunk/src/tools/ctoolspre11181.dita Thu Aug 12 16:29:26 2010
@@ -30,5 +30,6 @@ tools and utilities covered in this book
<li>sysinfo</li>
<li>dblook</li>
<li>SignatureChecker</li>
+<li>PlanExporter</li>
</ul></p>
</conbody></concept>
Modified: db/derby/docs/trunk/src/tools/ctoolspre23947.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/tools/ctoolspre23947.dita?rev=984851&r1=984850&r2=984851&view=diff
==============================================================================
--- db/derby/docs/trunk/src/tools/ctoolspre23947.dita (original)
+++ db/derby/docs/trunk/src/tools/ctoolspre23947.dita Thu Aug 12 16:29:26 2010
@@ -44,6 +44,9 @@ either a console or a file.</p></li>
information for a tool that identifies any SQL functions
and procedures in a database that do not follow the SQL Standard argument
matching rules.</p></li>
+<li><xref href="ctoolsplanexp.dita#ctoolsplanexp"></xref> <p>Reference
+information for a tool that exports query plan data for further
+analysis.</p></li>
</ul></p>
</conbody>
</concept>
Modified: db/derby/docs/trunk/src/tools/ctoolsusingplanexp.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/tools/ctoolsusingplanexp.dita?rev=984851&r1=984850&r2=984851&view=diff
==============================================================================
--- db/derby/docs/trunk/src/tools/ctoolsusingplanexp.dita (original)
+++ db/derby/docs/trunk/src/tools/ctoolsusingplanexp.dita Thu Aug 12 16:29:26 2010
@@ -27,86 +27,72 @@ limitations under the License.
<p>Before you run the <codeph>PlanExporter</codeph> tool, make sure that
your classpath contains the
<ph conref="../conrefs.dita#prod/productshortname"></ph> jar files, including
-<i>derbytools.jar</i>.</p>
-<p>Other than that you need <i>xalan.jar</i> in your classpath as well.</p>
+<i>derbytools.jar</i>. You must also have <i>xalan.jar</i> in your classpath.</p>
<p>Before you run the <codeph>PlanExporter</codeph> tool, you must capture the
-<codeph>STMT_ID</codeph> of the query you have executed from
-<codeph>SYSXPLAIN_STATEMENTS system table</codeph>. You can do it like
-this: </p>
-<ul>
-<li><b>Use XPLAIN styles to capture the runtime statistics:</b>
-<p>Refer to the "SYSCS_UTIL.SYSCS_SET_XPLAIN_SCHEMA system procedure" in
+<codeph>stmt_id</codeph> of the query you have executed from
+<codeph>SYSXPLAIN_STATEMENTS system table</codeph>. To do so, follow these
+steps:</p>
+<ol>
+<li><b>Use XPLAIN styles to capture the runtime statistics.</b>
+<p>Refer to "SYSCS_UTIL.SYSCS_SET_XPLAIN_SCHEMA system procedure" in the
<ph conref="../conrefs.dita#pub/citref"></ph> to see how to do this.</p>
-<note> You have to remember the <codeph>SCHEMA_NAME</codeph>.</note> </li>
-<li><b>Query <codeph>SYSXPLAIN_STATEMENTS system table</codeph>
-to grab the <codeph>STMT_ID</codeph> of the query you have executed.</b>
-<note> Refer to "SYSXPLAIN_STATEMENTS system table" in
+<note> You must remember the <codeph>schema_name</codeph>.</note> </li>
+<li><b>Query the SYSXPLAIN_STATEMENTS system table
+to obtain the <codeph>stmt_id</codeph> of the query you have executed.</b>
+<p>Refer to "SYSXPLAIN_STATEMENTS system table" in the
<ph conref="../conrefs.dita#pub/citref"></ph> for information
-about <codeph>SYSXPLAIN_STATEMENTS system table</codeph>.</note>
+about the SYSXPLAIN_STATEMENTS system table.</p>
</li>
-</ul>
-<p>You can run the tool as follows inside the directory where your database
+</ol>
+<p>You can run the tool as follows in the directory where your database
is located.</p>
<codeblock>
- java org.apache.derby.tools.PlanExporter jdbc:derby:<i>database_name
- username password SCHEMA_NAME STMT_ID</i> [<i>arguments</i>]
+java org.apache.derby.tools.PlanExporter jdbc:derby:<i>database_name
+ username password schema_name stmt_id</i> <i>options</i>
</codeblock>
-<p>[<i>arguments</i>] can be passed according to your requirement. Consider
-following possible scenarios:</p>
-<p>If your requirement is,</p>
+<p>The <i>options</i> can be passed according to your requirements. Consider
+the following possible scenarios:</p>
<ul>
<li>
-<b>only to generate a XML file of the query plan:</b>
-<p>You can pass
-<codeblock> -xml {path}</codeblock> argument.</p>
+<p>To generate an XML file of the query plan, specify the following option:</p>
+<codeblock>-xml <i>path</i></codeblock>
+<p>The <i>path</i> can be either absolute or relative. If the root filename does
+not have a suffix, the tool appends <codeph>.xml</codeph>.</p>
</li>
<li>
-<b>to generate a plain HTML file of the query plan:</b>
-<p>Simply you can use the default simple style sheet provided with
-<ph conref="../conrefs.dita#prod/productshortname"></ph> if you
-use following arguments: </p>
-<ul>
-<li>You can pass
-<codeblock> -html {path}</codeblock> argument.</li>
-<li>You can pass
-<codeblock> -xml {path} -html {path}</codeblock>
-arguments, if you want to generate the XML file as well.</li>
-</ul>
-<p>If you have a different style sheet, which does not contain any
-<i>javascript</i> functions, you can use following arguments: </p>
-<ul>
-<li>You can pass
-<codeblock> -xsl {path} -html {path}</codeblock>
-arguments. </li>
-<li>You can pass
-<codeblock> -xml {path} -xsl {path} -html {path}</codeblock> arguments,
-if you want to generate the XML file as well.</li>
-</ul>
+<p>To generate a plain HTML file of the query plan, you can use the default
+simple style sheet provided with
+<ph conref="../conrefs.dita#prod/productshortname"></ph>. Specify the following
+options:</p>
+<codeblock>-html <i>path</i></codeblock>
+<p>If the root filename does not have a suffix, the tool appends
+<codeph>.html</codeph>.</p>
+<p>To generate the XML file as well, specify the following options:</p>
+<codeblock>-xml <i>path</i> -html <i>path</i></codeblock>
+<p>To use a different style sheet that does not contain any <i>javascript</i>
+functions, specify the following options:</p>
+<codeblock>-xsl <i>path</i> -html <i>path</i></codeblock>
+<p>To generate the XML file as well, specify the following options:</p>
+<codeblock>-xml <i>path</i> -xsl <i>path</i> -html <i>path</i></codeblock>
</li>
<li>
-<b>to generate an advanced view of the query plan:</b>
-<p>You can use advanced XSL style sheets provided with
-<ph conref="../conrefs.dita#prod/productshortname"></ph> or
-you can specify a style sheet created by you, if you use
-following argument:</p>
-<ul>
-<li>You can pass
-<codeblock> -adv -xsl {file_name} -xml {path}</codeblock>
-arguments.
+<p>To generate an advanced view of the query plan, you can use advanced XSL
+style sheets provided with
+<ph conref="../conrefs.dita#prod/productshortname"></ph>, or you can specify a
+style sheet created by you. To do this, specify the following options:</p>
+<codeblock>-adv -xsl <i>fileName</i> -xml <i>path</i></codeblock>
<note>
<ul>
-<li>When you use <codeph>-adv</codeph> feature, you must copy the advanced
-XSL style sheet into the current directory. Thus, you must only specify
-the name of the style sheet.</li>
-<li>Generating a HTML is not supported when you use <codeph>-adv</codeph>
-feature of the <codeph>PlanExporter</codeph> tool. But you can always open
-the generated XML file, in your web browser, then your browser will do the
+<li>Before you use the <codeph>-adv</codeph> feature, you must copy the advanced
+XSL style sheet into the current directory. Thus, you must specify only
+the name of the style sheet, not the path.</li>
+<li>Generating HTML is not supported when you use the <codeph>-adv</codeph>
+feature of the <codeph>PlanExporter</codeph> tool. But if you open
+the generated XML file in a web browser, the browser will do the
necessary transformation.</li>
</ul>
</note>
</li>
</ul>
-</li>
-</ul>
</conbody>
</concept>
Modified: db/derby/docs/trunk/src/tools/derbytools.ditamap
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/tools/derbytools.ditamap?rev=984851&r1=984850&r2=984851&view=diff
==============================================================================
--- db/derby/docs/trunk/src/tools/derbytools.ditamap (original)
+++ db/derby/docs/trunk/src/tools/derbytools.ditamap Thu Aug 12 16:29:26 2010
@@ -349,9 +349,10 @@ limitations under the License.
<topicref collection-type="family" href="ctoolssigcheck.dita" navtitle="SignatureChecker">
<topicref href="ctoolsusingsigcheck.dita" navtitle="Using SignatureChecker"></topicref>
</topicref>
-<topicref collection-type="family" href="ctoolsplanexp.dita" navtitle="PlanExporter Tool">
+<topicref collection-type="family" href="ctoolsplanexp.dita" navtitle="PlanExporter">
<topicref href="ctoolsusingplanexp.dita" navtitle="Using PlanExporter"></topicref>
-<topicref href="rtoolsplanexpexamples.dita" navtitle="PlanExporter Examples"></topicref>
+<topicref href="rtoolsplanexpxmlformat.dita" navtitle="PlanExporter XML format"></topicref>
+<topicref href="rtoolsplanexpexamples.dita" navtitle="PlanExporter example"></topicref>
</topicref>
<topicref href="rtoolstrademderby.dita" navtitle="Trademarks"></topicref>
</map>
Modified: db/derby/docs/trunk/src/tools/rtoolsplanexpexamples.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/tools/rtoolsplanexpexamples.dita?rev=984851&r1=984850&r2=984851&view=diff
==============================================================================
--- db/derby/docs/trunk/src/tools/rtoolsplanexpexamples.dita (original)
+++ db/derby/docs/trunk/src/tools/rtoolsplanexpexamples.dita Thu Aug 12 16:29:26 2010
@@ -19,57 +19,55 @@ See the License for the specific languag
limitations under the License.
-->
<reference id="rtoolsplanexpexamples" xml:lang="en-us">
-<title>PlanExporter Examples</title>
+<title>PlanExporter example</title>
<prolog><metadata>
-<keywords><indexterm>PlanExporter<indexterm>Examples</indexterm></indexterm>
-<indexterm>Examples<indexterm>PlanExporter</indexterm></indexterm>
+<keywords><indexterm>PlanExporter<indexterm>example</indexterm></indexterm>
+<indexterm>examples<indexterm>PlanExporter</indexterm></indexterm>
</keywords>
</metadata></prolog>
<refbody>
-<section><p>The following example demonstrates a complete procedure
-that you must follow in order to use <codeph>PlanExporter</codeph> tool.</p>
+<section><p>This example shows the steps that you must follow in order
+to use the <codeph>PlanExporter</codeph> tool.</p>
</section>
<example>
-<ul>
-<li>Move to the directory where your database has created. </li>
-<li>Run <codeph>ij</codeph> tool:
-<codeblock> java org.apache.derby.tools.ij</codeblock>
+<ol>
+<li>Move to the directory where your database was created.</li>
+<li>Run the <codeph>ij</codeph> tool:
+<codeblock>java org.apache.derby.tools.ij</codeblock>
</li>
<li>Create a connection to the database:
-<codeblock> CONNECT 'jdbc:derby:myDb;create=false';</codeblock>
-<note>You can use <ph conref="../conrefs.dita#prod/productshortname"></ph>
+<codeblock>CONNECT 'jdbc:derby:myDb;create=false';</codeblock>
+<note>You can use a <ph conref="../conrefs.dita#prod/productshortname"></ph>
client/server database as well. </note>
</li>
<li>Use XPLAIN styles:
<codeblock>
- CALL SYSCS_UTIL.SYSCS_SET_RUNTIMESTATISTICS(1);
- CALL SYSCS_UTIL.SYSCS_SET_XPLAIN_SCHEMA('MY_SCHEMA');
- select * from my_table;
- CALL SYSCS_UTIL.SYSCS_SET_RUNTIMESTATISTICS(0);
- CALL SYSCS_UTIL.SYSCS_SET_XPLAIN_SCHEMA('');
+CALL SYSCS_UTIL.SYSCS_SET_RUNTIMESTATISTICS(1);
+CALL SYSCS_UTIL.SYSCS_SET_XPLAIN_SCHEMA('MY_SCHEMA');
+select * from my_table;
+CALL SYSCS_UTIL.SYSCS_SET_RUNTIMESTATISTICS(0);
+CALL SYSCS_UTIL.SYSCS_SET_XPLAIN_SCHEMA('');
</codeblock>
</li>
-<li>Grab the <codeph>stmt_id</codeph> of the query:
+<li>Obtain the <codeph>stmt_id</codeph> of the query:
<codeblock>
- select stmt_text, stmt_id from MY_SCHEMA.SYSXPLAIN_STATEMENTS;
- exit;
+select stmt_text, stmt_id from MY_SCHEMA.SYSXPLAIN_STATEMENTS;
+exit;
</codeblock>
-<p>Now find the stmt_id of the executed query, from the displaying
-results, and note it down. My case it is
-<codeph>9ac8804c-0129-cc31-ca9a-00000047f1e8</codeph>.</p>
+<p>Now find the <codeph>stmt_id</codeph> of the executed query in the displayed
+results and note it down. It looks something like this:</p>
+<codeblock>9ac8804c-0129-cc31-ca9a-00000047f1e8</codeblock>
</li>
<li>Run the <codeph>PlanExporter</codeph> tool in the same location:
-<codeblock>
- java org.apache.derby.tools.PlanExporter jdbc:derby:myDb "" "" MY_SCHEMA
- 9ac8804c-0129-cc31-ca9a-00000047f1e8 -html plain_html;
-</codeblock>
-<note>Here I have used the default style sheet provided with
+<codeblock>java org.apache.derby.tools.PlanExporter jdbc:derby:myDb "" "" MY_SCHEMA
+ 9ac8804c-0129-cc31-ca9a-00000047f1e8 -html plain_html;</codeblock>
+<p>This command uses the default style sheet provided with
<ph conref="../conrefs.dita#prod/productshortname"></ph>, and the HTML
-file will be generated at the same location, since I have not specified
-a different path. The name of the HTML file generated is <i>plain_html.html</i>
-</note>
+file will be generated at the same location, since the command does not specify
+a different path. The name of the HTML file generated is <i>plain_html.html</i>.
+</p>
</li>
-</ul>
+</ol>
</example>
</refbody>
</reference>
Added: db/derby/docs/trunk/src/tools/rtoolsplanexpxmlformat.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/tools/rtoolsplanexpxmlformat.dita?rev=984851&view=auto
==============================================================================
--- db/derby/docs/trunk/src/tools/rtoolsplanexpxmlformat.dita (added)
+++ db/derby/docs/trunk/src/tools/rtoolsplanexpxmlformat.dita Thu Aug 12 16:29:26 2010
@@ -0,0 +1,136 @@
+<?xml version="1.0" encoding="utf-8"?>
+
+<!DOCTYPE reference PUBLIC "-//OASIS//DTD DITA Reference//EN"
+ "../dtd/reference.dtd">
+<!--
+Licensed to the Apache Software Foundation (ASF) under one or more
+contributor license agreements. See the NOTICE file distributed with
+this work for additional information regarding copyright ownership.
+The ASF licenses this file to You under the Apache License, Version 2.0
+(the "License"); you may not use this file except in compliance with
+the License. You may obtain a copy of the License at
+
+http://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing, software
+distributed under the License is distributed on an "AS IS" BASIS,
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+See the License for the specific language governing permissions and
+limitations under the License.
+-->
+<reference id="rtoolsplanexpxmlformat" xml:lang="en-us">
+<title>PlanExporter XML format</title>
+<prolog><metadata>
+<keywords><indexterm>PlanExporter<indexterm>XML</indexterm></indexterm>
+<indexterm>XML<indexterm>PlanExporter</indexterm></indexterm>
+</keywords>
+</metadata></prolog>
+<refbody>
+<section><p>The <codeph>PlanExporter</codeph> tool extracts
+the query plan of an executed query as a XML document by using the
+statistics captured from
+<ph conref="../conrefs.dita#prod/productshortname"></ph> XPLAIN style
+tables.</p>
+</section>
+<section><p>An XML document generated by the <codeph>PlanExporter</codeph> tool
+has the following structure.</p></section>
+<section>
+<ul>
+<li><b>The basic tree structure:</b>
+<codeblock>
+plan - (The root of the XML tree)
+|
+|-- statement - (first child - The query executed)
+|
+|-- details - (second child - Contains the query plan)
+</codeblock>
+</li>
+<li><b>The <codeph>statement</codeph> element:</b>
+<p>This element has only its value. That value implies the
+query executed, as retrieved from the STMT_TEXT row of SYSXPLAIN_STATEMENTS
+table.</p>
+<p>For example:</p>
+<codeblock><statement>select * from my_table</statement>
+</codeblock>
+</li>
+<li><b>The <codeph>details</codeph> element:</b>
+<p>This element contains the query plan, as a tree structure
+of plan nodes.</p>
+<p>For a particular query there is only one root plan node.</p></li>
+<li><b>A <codeph>node</codeph> element:</b>
+<p>Contains the details of a plan node of the query plan.
+This element can contain zero or many child elements of the
+same type (<codeph>node</codeph> elements). </p>
+<p>This element contains one or more attributes, given that
+they are not null. The possible attributes and
+their meanings are as follows.</p>
+<simpletable relcolwidth="1* 4*">
+<sthead>
+<stentry>Attribute Name</stentry>
+<stentry>Meaning</stentry>
+</sthead>
+<strow>
+<stentry><codeph>name</codeph></stentry>
+<stentry>Name of the plan node</stentry>
+</strow>
+<strow>
+<stentry><codeph>input_rows</codeph></stentry>
+<stentry>Retrieved from the INPUT_ROWS row of the SYSXPLAIN_RESULTSETS system
+table</stentry>
+</strow>
+<strow>
+<stentry><codeph>returned_rows</codeph></stentry>
+<stentry>Retrieved from the RETURNED_ROWS row of the SYSXPLAIN_RESULTSETS system
+table</stentry>
+</strow>
+<strow>
+<stentry><codeph>no_opens</codeph></stentry>
+<stentry>Retrieved from the NO_OPENS row of the SYSXPLAIN_RESULTSETS system
+table</stentry>
+</strow>
+<strow>
+<stentry><codeph>visited_pages</codeph></stentry>
+<stentry>Retrieved from the NO_VISITED_PAGES row of the SYSXPLAIN_SCAN_PROPS
+system table</stentry>
+</strow>
+<strow>
+<stentry><codeph>scan_qualifiers</codeph></stentry>
+<stentry>Retrieved from the SCAN_QUALIFIERS row of the SYSXPLAIN_SCAN_PROPS
+system table</stentry>
+</strow>
+<strow>
+<stentry><codeph>next_qualifiers</codeph></stentry>
+<stentry>Retrieved from the NEXT_QUALIFIERS row of the SYSXPLAIN_SCAN_PROPS
+system table</stentry>
+</strow>
+<strow>
+<stentry><codeph>scanned_object</codeph></stentry>
+<stentry>Retrieved from the SCAN_OBJECT_NAME row of the SYSXPLAIN_SCAN_PROPS
+system table</stentry>
+</strow>
+<strow>
+<stentry><codeph>scan_type</codeph></stentry>
+<stentry>Retrieved from the SCAN_TYPE row of the SYSXPLAIN_SCAN_PROPS
+system table</stentry>
+</strow>
+<strow>
+<stentry><codeph>sort_type</codeph></stentry>
+<stentry>Retrieved from the SORT_TYPE row of the SYSXPLAIN_SORT_PROPS system
+table</stentry>
+</strow>
+<strow>
+<stentry><codeph>sorter_output</codeph></stentry>
+<stentry>Retrieved from the NO_OUTPUT_ROWS row of the SYSXPLAIN_SORT_PROPS
+system table</stentry>
+</strow>
+</simpletable>
+<p>For example:
+<codeblock><node name="TABLESCAN" returned_rows="100000" no_opens="1"
+visited_pages="2165" scan_qualifiers="None" scanned_object="USERS"
+scan_type="HEAP" ></codeblock>
+</p>
+</li>
+</ul>
+</section>
+</refbody>
+</reference>
Propchange: db/derby/docs/trunk/src/tools/rtoolsplanexpxmlformat.dita
------------------------------------------------------------------------------
svn:eol-style = native