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 sc...@apache.org on 2007/03/30 17:14:53 UTC
svn commit: r524117 [2/3] - /db/derby/docs/trunk/src/tuning/
Modified: db/derby/docs/trunk/src/tuning/ctunpropref11181.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/tuning/ctunpropref11181.dita?view=diff&rev=524117&r1=524116&r2=524117
==============================================================================
--- db/derby/docs/trunk/src/tuning/ctunpropref11181.dita (original)
+++ db/derby/docs/trunk/src/tuning/ctunpropref11181.dita Fri Mar 30 08:14:48 2007
@@ -21,7 +21,7 @@
<prolog>
</prolog>
<conbody>
-<p>This guide, <cite><ph conref="tunconrefs.dita#pub/cittuning"></ph></cite>, explains how to set properties
+<p>This guide, <cite><ph conref="../conrefs.dita#pub/cittuning"></ph></cite>, explains how to set properties
to configure and tune systems, databases, specific tables and indexes, and
queries. This guide also provides performance tuning tips and an in-depth
study of query optimization and performance issues.</p>
Modified: db/derby/docs/trunk/src/tuning/ctunpropref22460.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/tuning/ctunpropref22460.dita?view=diff&rev=524117&r1=524116&r2=524117
==============================================================================
--- db/derby/docs/trunk/src/tuning/ctunpropref22460.dita (original)
+++ db/derby/docs/trunk/src/tuning/ctunpropref22460.dita Fri Mar 30 08:14:48 2007
@@ -21,10 +21,10 @@
<prolog>
</prolog>
<conbody>
-<p>This book is a reference for <ph conref="tunconrefs.dita#prod/productshortname"></ph> users, typically application developers. <ph conref="tunconrefs.dita#prod/productshortname"></ph> users
+<p>This book is a reference for <ph conref="../conrefs.dita#prod/productshortname"></ph> users, typically application developers. <ph conref="../conrefs.dita#prod/productshortname"></ph> users
who are not familiar with the SQL standard or the Java programming language
will benefit from consulting books on those topics. </p>
-<p><ph conref="tunconrefs.dita#prod/productshortname"></ph> users who want a how-to approach to working with <ph conref="tunconrefs.dita#prod/productshortname"></ph> or
-an introduction to <ph conref="tunconrefs.dita#prod/productshortname"></ph> concepts should read the <cite><ph conref="tunconrefs.dita#pub/citdevelop"></ph></cite>. This book is for users who want to optimize and tune their application's
+<p><ph conref="../conrefs.dita#prod/productshortname"></ph> users who want a how-to approach to working with <ph conref="../conrefs.dita#prod/productshortname"></ph> or
+an introduction to <ph conref="../conrefs.dita#prod/productshortname"></ph> concepts should read the <cite><ph conref="../conrefs.dita#pub/citdevelop"></ph></cite>. This book is for users who want to optimize and tune their application's
performance.</p>
</conbody></concept>
Modified: db/derby/docs/trunk/src/tuning/ctunpropref23947.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/tuning/ctunpropref23947.dita?view=diff&rev=524117&r1=524116&r2=524117
==============================================================================
--- db/derby/docs/trunk/src/tuning/ctunpropref23947.dita (original)
+++ db/derby/docs/trunk/src/tuning/ctunpropref23947.dita Fri Mar 30 08:14:48 2007
@@ -26,15 +26,15 @@
<li><i><xref href="ctunsetprop34818.dita#ctunsetprop34818"/></i>
<p>An overview of how you set properties.</p></li>
<li><i><xref href="ctunperf22457.dita#ctunperf22457"/></i>
-<p>Quick tips on how to improve the performance of <ph conref="tunconrefs.dita#prod/productshortname"></ph> applications.</p></li>
+<p>Quick tips on how to improve the performance of <ph conref="../conrefs.dita#prod/productshortname"></ph> applications.</p></li>
<li><i><xref href="ctundepth39739.dita#ctundepth39739"/></i>
-<p>A more in-depth discussion of how to improve the performance of <ph conref="tunconrefs.dita#prod/productshortname"></ph> applications.</p></li>
+<p>A more in-depth discussion of how to improve the performance of <ph conref="../conrefs.dita#prod/productshortname"></ph> applications.</p></li>
<li><i><xref href="ctunoptimz39739.dita#ctunoptimz39739"/></i>
-<p>An in-depth study of how <ph conref="tunconrefs.dita#prod/productshortname"></ph> executes queries, how the optimizer works,
+<p>An in-depth study of how <ph conref="../conrefs.dita#prod/productshortname"></ph> executes queries, how the optimizer works,
and how to tune query execution.</p></li>
<li><i><xref href="ctunstats18908.dita#ctunstats18908"/></i></li>
<li><i><xref href="ctuntransform13966.dita#ctuntransform13966"/></i>
-<p>Reference on how <ph conref="tunconrefs.dita#prod/productshortname"></ph> internally transforms some SQL statements
+<p>Reference on how <ph conref="../conrefs.dita#prod/productshortname"></ph> internally transforms some SQL statements
for performance reasons. Not of interest to the general user.</p></li>
</ul></p>
</conbody></concept>
Modified: db/derby/docs/trunk/src/tuning/ctunsetprop1003847.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/tuning/ctunsetprop1003847.dita?view=diff&rev=524117&r1=524116&r2=524117
==============================================================================
--- db/derby/docs/trunk/src/tuning/ctunsetprop1003847.dita (original)
+++ db/derby/docs/trunk/src/tuning/ctunsetprop1003847.dita Fri Mar 30 08:14:48 2007
@@ -26,14 +26,14 @@
</prolog>
<conbody>
<p>You can set system-wide properties as parameters to the JVM command line
-when starting up the application or framework in which <ph conref="tunconrefs.dita#prod/productshortname"></ph> is embedded.
+when starting up the application or framework in which <ph conref="../conrefs.dita#prod/productshortname"></ph> is embedded.
<ul>
<li><i>IBM Application Developer Kits</i>
<p>With the IBM®
SDK, you set JVM system properties by using a <i>-D</i> flag
on the Java command line. For example:
-<codeblock><b>java -Dderby.system.home=C:\home\<ph conref="tunconrefs.dita#prod/productshortname"></ph>\
+<codeblock><b>java -Dderby.system.home=C:\home\<ph conref="../conrefs.dita#prod/productshortname"></ph>\
-Dderby.storage.pageSize=8192 JDBCTest</b></codeblock></p></li>
</ul></p>
<p>For other JVMs, see the JVM-specific documentation on setting system properties.</p>
Modified: db/derby/docs/trunk/src/tuning/ctunsetprop11108.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/tuning/ctunsetprop11108.dita?view=diff&rev=524117&r1=524116&r2=524117
==============================================================================
--- db/derby/docs/trunk/src/tuning/ctunsetprop11108.dita (original)
+++ db/derby/docs/trunk/src/tuning/ctunsetprop11108.dita Fri Mar 30 08:14:48 2007
@@ -19,7 +19,7 @@
-->
<concept id="ctunsetprop11108" xml:lang="en-us">
<title>Properties overview</title>
-<shortdesc><ph conref="tunconrefs.dita#prod/productshortname"></ph> lets you
+<shortdesc><ph conref="../conrefs.dita#prod/productshortname"></ph> lets you
configure behavior or attributes of a system, a specific database, or a specific <i>conglomerate</i> (a
table or index) through the use of properties.</shortdesc>
<prolog></prolog>
Modified: db/derby/docs/trunk/src/tuning/ctunsetprop11561.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/tuning/ctunsetprop11561.dita?view=diff&rev=524117&r1=524116&r2=524117
==============================================================================
--- db/derby/docs/trunk/src/tuning/ctunsetprop11561.dita (original)
+++ db/derby/docs/trunk/src/tuning/ctunsetprop11561.dita Fri Mar 30 08:14:48 2007
@@ -22,13 +22,13 @@
</prolog>
<conbody>
<p>You can set properties programmatically-either in application code
-before booting the <ph conref="tunconrefs.dita#prod/productshortname"></ph> driver or as a command-line option to the JVM
-when booting the application that starts up <ph conref="tunconrefs.dita#prod/productshortname"></ph>. When you set properties
+before booting the <ph conref="../conrefs.dita#prod/productshortname"></ph> driver or as a command-line option to the JVM
+when booting the application that starts up <ph conref="../conrefs.dita#prod/productshortname"></ph>. When you set properties
programmatically, these properties persist only for the duration of the application.
-Properties set programmatically are not written to the <i>derby.properties</i> file or made persistent in any other way by <ph conref="tunconrefs.dita#prod/productshortname"></ph>.
+Properties set programmatically are not written to the <i>derby.properties</i> file or made persistent in any other way by <ph conref="../conrefs.dita#prod/productshortname"></ph>.
<note>Setting properties programmatically works only for the application
-that starts up <ph conref="tunconrefs.dita#prod/productshortname"></ph>; for example, for an application in an embedded
+that starts up <ph conref="../conrefs.dita#prod/productshortname"></ph>; for example, for an application in an embedded
environment or for the application server that starts up a server product.
It does not work for client applications connecting to a server that is running.</note></p>
</conbody></concept>
Modified: db/derby/docs/trunk/src/tuning/ctunsetprop12821.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/tuning/ctunsetprop12821.dita?view=diff&rev=524117&r1=524116&r2=524117
==============================================================================
--- db/derby/docs/trunk/src/tuning/ctunsetprop12821.dita (original)
+++ db/derby/docs/trunk/src/tuning/ctunsetprop12821.dita Fri Mar 30 08:14:48 2007
@@ -30,7 +30,7 @@
</prolog>
<conbody>
<p>Database-wide properties, which affect a single database, are stored within
-the database itself. This allows different databases within a single <ph conref="tunconrefs.dita#prod/productshortname"></ph> system
+the database itself. This allows different databases within a single <ph conref="../conrefs.dita#prod/productshortname"></ph> system
to have different properties and ensures that the properties are correctly
set when a database is moved away from its original system or copied.
<note>You should use database-wide properties wherever possible for ease
@@ -41,8 +41,8 @@
passing the name of the property and the value.</p>
<p>To check the current value of a property, you connect to the database,
create a statement, and then use the <codeph>SYSCS_UTIL.SYSCS_GET_DATABASE_PROPERTY</codeph> function, passing in the name of the property. </p>
-<p>If you specify an invalid value, <ph conref="tunconrefs.dita#prod/productshortname"></ph> uses the default value for
+<p>If you specify an invalid value, <ph conref="../conrefs.dita#prod/productshortname"></ph> uses the default value for
the property.</p>
-<p>See the <cite><ph conref="tunconrefs.dita#pub/citref"></ph></cite> for more information on how to use these system
+<p>See the <cite><ph conref="../conrefs.dita#pub/citref"></ph></cite> for more information on how to use these system
functions and procedures.</p>
</conbody></concept>
Modified: db/derby/docs/trunk/src/tuning/ctunsetprop13074.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/tuning/ctunsetprop13074.dita?view=diff&rev=524117&r1=524116&r2=524117
==============================================================================
--- db/derby/docs/trunk/src/tuning/ctunsetprop13074.dita (original)
+++ db/derby/docs/trunk/src/tuning/ctunsetprop13074.dita Fri Mar 30 08:14:48 2007
@@ -29,10 +29,10 @@
which must be placed in the directory specified by the <i>derby.system.home</i> property.
There should be one <i>derby.properties</i> file per system, not per database.
The file must be created in the system directory. In a client/server environment,
-that directory is on the server. (For more information about a <ph conref="tunconrefs.dita#prod/productshortname"></ph> system
-and the system directory, see "<ph conref="tunconrefs.dita#prod/productshortname"></ph> System"
-in the <cite><ph conref="tunconrefs.dita#pub/citdevelop"></ph></cite>.)</p>
-<p><ph conref="tunconrefs.dita#prod/productshortname"></ph> does <i>not</i>:
+that directory is on the server. (For more information about a <ph conref="../conrefs.dita#prod/productshortname"></ph> system
+and the system directory, see "<ph conref="../conrefs.dita#prod/productshortname"></ph> System"
+in the <cite><ph conref="../conrefs.dita#pub/citdevelop"></ph></cite>.)</p>
+<p><ph conref="../conrefs.dita#prod/productshortname"></ph> does <i>not</i>:
<ul>
<li>Provide this file</li>
<li>Automatically create this file for you</li>
@@ -45,7 +45,7 @@
derby.storage.pageReservedSpace=60</b></codeblock></p>
<p>Properties set this way are persistent for the system until changed, until
the file is removed from the system, or until the system is booted in some
-other directory (in which case <ph conref="tunconrefs.dita#prod/productshortname"></ph> would
+other directory (in which case <ph conref="../conrefs.dita#prod/productshortname"></ph> would
be looking for <i>derby.properties</i> in that new directory). If a database
is removed from a system, system-wide properties do not "travel" with the
database unless explicitly set again.</p>
Modified: db/derby/docs/trunk/src/tuning/ctunsetprop32443.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/tuning/ctunsetprop32443.dita?view=diff&rev=524117&r1=524116&r2=524117
==============================================================================
--- db/derby/docs/trunk/src/tuning/ctunsetprop32443.dita (original)
+++ db/derby/docs/trunk/src/tuning/ctunsetprop32443.dita Fri Mar 30 08:14:48 2007
@@ -26,9 +26,9 @@
</metadata>
</prolog>
<conbody>
-<p><ph conref="tunconrefs.dita#prod/productshortname"></ph> allows you a lot of freedom in configuring your system. This
+<p><ph conref="../conrefs.dita#prod/productshortname"></ph> allows you a lot of freedom in configuring your system. This
freedom can be confusing if you do not understand how properties work. You
-also have the option of not setting any and instead using the <ph conref="tunconrefs.dita#prod/productshortname"></ph> defaults,
+also have the option of not setting any and instead using the <ph conref="../conrefs.dita#prod/productshortname"></ph> defaults,
which are tuned for a single-user embedded system.</p>
<p>Imagine the following scenario of an embedded environment:</p>
<p>Your system has a <i>derby.properties</i> file, a text
@@ -41,7 +41,7 @@
<codeblock><b>java -Dderby.system.home=c:\system_directory MyApp</b></codeblock></p>
<p>You then create a new table:
<codeblock><b>CREATE TABLE table1 (a INT, b VARCHAR(10))</b></codeblock></p>
-<p><ph conref="tunconrefs.dita#prod/productshortname"></ph> takes the page size of 8192 from the system-wide properties
+<p><ph conref="../conrefs.dita#prod/productshortname"></ph> takes the page size of 8192 from the system-wide properties
set in the <i>derby.properties</i> file, since the property
has not been set any other way.</p>
<p>You shut down and then restart your application, setting the value of <i>derby.storage.pageSize</i> to 4096 programmatically,
@@ -69,7 +69,7 @@
<codeblock><b>java -Dderby.system.home=c:\system_directory MyApp</b></codeblock></p>
<p>You then create another table:
<codeblock><b>CREATE TABLE table4 (a INT, b VARCHAR(10))</b></codeblock></p>
-<p><ph conref="tunconrefs.dita#prod/productshortname"></ph> uses the persistent database-wide property of 32768 for this
+<p><ph conref="../conrefs.dita#prod/productshortname"></ph> uses the persistent database-wide property of 32768 for this
table, since the database-wide property set in the previous session is persistent
and overrides the system-wide property set in the <i>derby.properties</i> file.</p>
<p>What you have is a situation in which three different tables each get a
Modified: db/derby/docs/trunk/src/tuning/ctunsetprop38343.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/tuning/ctunsetprop38343.dita?view=diff&rev=524117&r1=524116&r2=524117
==============================================================================
--- db/derby/docs/trunk/src/tuning/ctunsetprop38343.dita (original)
+++ db/derby/docs/trunk/src/tuning/ctunsetprop38343.dita Fri Mar 30 08:14:48 2007
@@ -27,8 +27,8 @@
</metadata>
</prolog>
<conbody>
-<p>In embedded mode, your application runs in the same JVM as <ph conref="tunconrefs.dita#prod/productshortname"></ph>,
-so you can also set system properties within an application using a <i>Properties</i> object before loading the <ph conref="tunconrefs.dita#prod/productshortname"></ph> JDBC driver. The following
+<p>In embedded mode, your application runs in the same JVM as <ph conref="../conrefs.dita#prod/productshortname"></ph>,
+so you can also set system properties within an application using a <i>Properties</i> object before loading the <ph conref="../conrefs.dita#prod/productshortname"></ph> JDBC driver. The following
example sets <i>derby.system.home</i> on Windows.
<codeblock><b>Properties p = System.getProperties();
p.put("derby.system.home", "C:\databases\sample");</b></codeblock></p>
Modified: db/derby/docs/trunk/src/tuning/ctunsetprop44147.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/tuning/ctunsetprop44147.dita?view=diff&rev=524117&r1=524116&r2=524117
==============================================================================
--- db/derby/docs/trunk/src/tuning/ctunsetprop44147.dita (original)
+++ db/derby/docs/trunk/src/tuning/ctunsetprop44147.dita Fri Mar 30 08:14:48 2007
@@ -21,14 +21,14 @@
<prolog>
</prolog>
<conbody>
-<note>Properties set in the <i>derby.properties</i> file and on the command line of the application that boots <ph conref="tunconrefs.dita#prod/productshortname"></ph> are <i>always</i> static, because <ph conref="tunconrefs.dita#prod/productshortname"></ph> reads this file and
+<note>Properties set in the <i>derby.properties</i> file and on the command line of the application that boots <ph conref="../conrefs.dita#prod/productshortname"></ph> are <i>always</i> static, because <ph conref="../conrefs.dita#prod/productshortname"></ph> reads this file and
those parameters only at startup.</note>
<p>Only properties set in the following ways have the potential to be dynamic:
<ul>
<li>As database-wide properties</li>
<li>As system-wide properties via a <i>Properties</i> object
-in the application in which the <ph conref="tunconrefs.dita#prod/productshortname"></ph> engine is embedded</li>
+in the application in which the <ph conref="../conrefs.dita#prod/productshortname"></ph> engine is embedded</li>
</ul></p>
<p>See <xref href="rtunproper32213.dita#rtunproper32213"/>, for information about specific
properties.</p>
Modified: db/derby/docs/trunk/src/tuning/ctunsetprop824451.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/tuning/ctunsetprop824451.dita?view=diff&rev=524117&r1=524116&r2=524117
==============================================================================
--- db/derby/docs/trunk/src/tuning/ctunsetprop824451.dita (original)
+++ db/derby/docs/trunk/src/tuning/ctunsetprop824451.dita Fri Mar 30 08:14:48 2007
@@ -28,7 +28,7 @@
</metadata>
</prolog>
<conbody>
-<p>You use properties to configure a <ph conref="tunconrefs.dita#prod/productshortname"></ph> system, database, or conglomerate.
+<p>You use properties to configure a <ph conref="../conrefs.dita#prod/productshortname"></ph> system, database, or conglomerate.
<ul>
<li><i>system-wide</i>
@@ -37,7 +37,7 @@
the entire system and all its databases and conglomerates, if this is applicable.
Some properties, such as error handling and automatic booting, can be configured
only in this way, since they apply to the entire system. (For information
-about the <ph conref="tunconrefs.dita#prod/productshortname"></ph> system, see the <cite><ph conref="tunconrefs.dita#pub/citdevelop"></ph></cite>.)</p>
+about the <ph conref="../conrefs.dita#prod/productshortname"></ph> system, see the <cite><ph conref="../conrefs.dita#pub/citdevelop"></ph></cite>.)</p>
<p>When
you change these properties, they affect any tables or indexes created <i>after</i> this change.</p></li>
<li><i>database-wide</i>
@@ -48,7 +48,7 @@
<p>When you
change these properties, they affect any tables or indexes created <i>after</i> this change.</p></li>
<li><i>conglomerate-specific</i>
-<p>Beginning with <ph conref="tunconrefs.dita#prod/productshortname"></ph>
+<p>Beginning with <ph conref="../conrefs.dita#prod/productshortname"></ph>
properties relating to conglomerates cannot be specified as part of the create-statement
for the object. These properties (for example, <i>derby.storage.pageSize</i>) must be set at the database level prior to executing the create-statement.
These storage-related properties take effect when you create a table or index,
Modified: db/derby/docs/trunk/src/tuning/ctunsetprop824615.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/tuning/ctunsetprop824615.dita?view=diff&rev=524117&r1=524116&r2=524117
==============================================================================
--- db/derby/docs/trunk/src/tuning/ctunsetprop824615.dita (original)
+++ db/derby/docs/trunk/src/tuning/ctunsetprop824615.dita Fri Mar 30 08:14:48 2007
@@ -27,12 +27,12 @@
</metadata>
</prolog>
<conbody>
-<p>Most properties are dynamic; that means you can set them while <ph conref="tunconrefs.dita#prod/productshortname"></ph> is
-running, and their values change without requiring a reboot of <ph conref="tunconrefs.dita#prod/productshortname"></ph>.
+<p>Most properties are dynamic; that means you can set them while <ph conref="../conrefs.dita#prod/productshortname"></ph> is
+running, and their values change without requiring a reboot of <ph conref="../conrefs.dita#prod/productshortname"></ph>.
In some cases, this change takes place immediately; in some cases, it takes
place at the next connection.</p>
<p>Some properties are static, which means changes to their values will not
-take effect while <ph conref="tunconrefs.dita#prod/productshortname"></ph> is running. You must restart or set them before
-(or while) starting <ph conref="tunconrefs.dita#prod/productshortname"></ph>.</p>
+take effect while <ph conref="../conrefs.dita#prod/productshortname"></ph> is running. You must restart or set them before
+(or while) starting <ph conref="../conrefs.dita#prod/productshortname"></ph>.</p>
<p>For more information, see <xref href="ctunsetprop44147.dita#ctunsetprop44147"/>.</p>
</conbody></concept>
Modified: db/derby/docs/trunk/src/tuning/ctunstats18908.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/tuning/ctunstats18908.dita?view=diff&rev=524117&r1=524116&r2=524117
==============================================================================
--- db/derby/docs/trunk/src/tuning/ctunstats18908.dita (original)
+++ db/derby/docs/trunk/src/tuning/ctunstats18908.dita Fri Mar 30 08:14:48 2007
@@ -33,7 +33,7 @@
<li>The optimizer knows "exactly" the number of rows that will be
scanned from disk for table scans (see <xref href="ctunstats57793.dita#ctunstats57793"/>).</li>
<li>For index scans, the optimizer must estimate the number of rows that will
-be scanned from disk. (see <xref href="ctunstats60669.dita#ctunstats60669"/>). <ph conref="tunconrefs.dita#prod/productshortname"></ph> might
+be scanned from disk. (see <xref href="ctunstats60669.dita#ctunstats60669"/>). <ph conref="../conrefs.dita#prod/productshortname"></ph> might
be able to use cardinality statistics to make a better estimate of the number
of rows that will be scanned from disk as described in this chapter.</li>
</ul></p>
Modified: db/derby/docs/trunk/src/tuning/ctunstats52657.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/tuning/ctunstats52657.dita?view=diff&rev=524117&r1=524116&r2=524117
==============================================================================
--- db/derby/docs/trunk/src/tuning/ctunstats52657.dita (original)
+++ db/derby/docs/trunk/src/tuning/ctunstats52657.dita Fri Mar 30 08:14:48 2007
@@ -25,10 +25,10 @@
</metadata>
</prolog>
<conbody>
-<p>In all other cases, <ph conref="tunconrefs.dita#prod/productshortname"></ph> uses a fixed number that attempts to describe
+<p>In all other cases, <ph conref="../conrefs.dita#prod/productshortname"></ph> uses a fixed number that attempts to describe
the percentage of rows that will probably be returned; it might not correspond
to the actual selectivity of the operation in every case. It is an assumption
-hard-wired into the <ph conref="tunconrefs.dita#prod/productshortname"></ph> system. These assumptions are shown in <xref href="ctunstats52657.dita#ctunstats52657/rtunstats405"/>.</p>
+hard-wired into the <ph conref="../conrefs.dita#prod/productshortname"></ph> system. These assumptions are shown in <xref href="ctunstats52657.dita#ctunstats52657/rtunstats405"/>.</p>
<table id="rtunstats405" frame="all">
<title>Selectivity for various operations for index scans
when search values are unknown in advance and statistics are not used</title>
Modified: db/derby/docs/trunk/src/tuning/ctunstats57373.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/tuning/ctunstats57373.dita?view=diff&rev=524117&r1=524116&r2=524117
==============================================================================
--- db/derby/docs/trunk/src/tuning/ctunstats57373.dita (original)
+++ db/derby/docs/trunk/src/tuning/ctunstats57373.dita Fri Mar 30 08:14:48 2007
@@ -21,7 +21,7 @@
<prolog>
</prolog>
<conbody>
-<p>For the following operations that you perform on a table, <ph conref="tunconrefs.dita#prod/productshortname"></ph> automatically
+<p>For the following operations that you perform on a table, <ph conref="../conrefs.dita#prod/productshortname"></ph> automatically
creates statistics. Those operations are:
<ul>
<li>(new index only) When you create a new index on an existing non-empty
@@ -29,7 +29,7 @@
<li>(new backing indexes only) When you add a primary key, unique, or foreign
key constraint to an existing non-empty table.</li>
</ul></p>
-<p>For other operations, <ph conref="tunconrefs.dita#prod/productshortname"></ph> automatically updates statistics for
+<p>For other operations, <ph conref="../conrefs.dita#prod/productshortname"></ph> automatically updates statistics for
the table and all indexes on the table if they are already exist. Those operations
are:
<ul>
Modified: db/derby/docs/trunk/src/tuning/ctunstats72938.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/tuning/ctunstats72938.dita?view=diff&rev=524117&r1=524116&r2=524117
==============================================================================
--- db/derby/docs/trunk/src/tuning/ctunstats72938.dita (original)
+++ db/derby/docs/trunk/src/tuning/ctunstats72938.dita Fri Mar 30 08:14:48 2007
@@ -25,10 +25,10 @@
</metadata>
</prolog>
<conbody>
-<p>Cardinality statistics are computed by the <ph conref="tunconrefs.dita#prod/productshortname"></ph> system and stored
+<p>Cardinality statistics are computed by the <ph conref="../conrefs.dita#prod/productshortname"></ph> system and stored
in the system tables. For information on when these statistics get created
or updated, see <xref href="ctunstats57373.dita#ctunstats57373"/>.</p>
-<p><ph conref="tunconrefs.dita#prod/productshortname"></ph> can use cardinality statistics if:
+<p><ph conref="../conrefs.dita#prod/productshortname"></ph> can use cardinality statistics if:
<ul>
<li>The statistics exist</li>
<li>The relevant columns in the WHERE column are leading columns in an index</li>
Modified: db/derby/docs/trunk/src/tuning/ctunstats848901.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/tuning/ctunstats848901.dita?view=diff&rev=524117&r1=524116&r2=524117
==============================================================================
--- db/derby/docs/trunk/src/tuning/ctunstats848901.dita (original)
+++ db/derby/docs/trunk/src/tuning/ctunstats848901.dita Fri Mar 30 08:14:48 2007
@@ -28,12 +28,12 @@
Stored row counts become inaccurate if there is a non-orderly shutdown (for
example, a power failure or other type of system crash).</p>
<p>You can correct the optimizer's row count without shutting down the
-system; <ph conref="tunconrefs.dita#prod/productshortname"></ph> sets the stored row count for a table to the correct value
+system; <ph conref="../conrefs.dita#prod/productshortname"></ph> sets the stored row count for a table to the correct value
whenever a query that does a full scan on the base conglomerate finishes.
For example, executing the following query sets the row count for table <i>Flights</i> to the correct value:
<codeblock><b>
SELECT * FROM Flights</b></codeblock></p>
-<p><ph conref="tunconrefs.dita#prod/productshortname"></ph> also sets the stored row count on a table to the correct value
+<p><ph conref="../conrefs.dita#prod/productshortname"></ph> also sets the stored row count on a table to the correct value
whenever a user creates a new index or primary key, unique, or foreign key
constraint on the table. This value is not guaranteed to be written to disk.</p>
</conbody></concept>
Modified: db/derby/docs/trunk/src/tuning/ctunstats849203.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/tuning/ctunstats849203.dita?view=diff&rev=524117&r1=524116&r2=524117
==============================================================================
--- db/derby/docs/trunk/src/tuning/ctunstats849203.dita (original)
+++ db/derby/docs/trunk/src/tuning/ctunstats849203.dita Fri Mar 30 08:14:48 2007
@@ -25,6 +25,6 @@
</metadata>
</prolog>
<conbody>
-<p><ph conref="tunconrefs.dita#prod/productshortname"></ph> determines the selectivity for a WHERE clause in one of two
+<p><ph conref="../conrefs.dita#prod/productshortname"></ph> determines the selectivity for a WHERE clause in one of two
ways.</p>
</conbody></concept>
Modified: db/derby/docs/trunk/src/tuning/ctunstats849251.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/tuning/ctunstats849251.dita?view=diff&rev=524117&r1=524116&r2=524117
==============================================================================
--- db/derby/docs/trunk/src/tuning/ctunstats849251.dita (original)
+++ db/derby/docs/trunk/src/tuning/ctunstats849251.dita Fri Mar 30 08:14:48 2007
@@ -25,14 +25,14 @@
</metadata>
</prolog>
<conbody>
-<p>When <ph conref="tunconrefs.dita#prod/productshortname"></ph> creates statistics for a table's index, it calculates
+<p>When <ph conref="../conrefs.dita#prod/productshortname"></ph> creates statistics for a table's index, it calculates
and stores in the system tables:
<ul>
<li>The number of rows in the table</li>
<li>The number of unique values for a set of columns for leading columns in
an index key, also known as <i>cardinality</i>. Leading columns
refers to the first column, or the first and second column, or the first,
-second, and third column of an index (and so on). <ph conref="tunconrefs.dita#prod/productshortname"></ph> cannot compute
+second, and third column of an index (and so on). <ph conref="../conrefs.dita#prod/productshortname"></ph> cannot compute
the number of columns for which a combination of the non-leading columns is
unique. </li>
</ul></p>
@@ -42,14 +42,14 @@
FLIGHT_ID,
SEGMENT_NUMBER,
FLIGHT_DATE)</b></codeblock></p>
-<p>For this index, <ph conref="tunconrefs.dita#prod/productshortname"></ph> keeps the following information:
+<p>For this index, <ph conref="../conrefs.dita#prod/productshortname"></ph> keeps the following information:
<ul>
<li>The number of rows in the table <i>FlightAvailability</i></li>
<li>The number of unique rows for the full key (<i>flight_id</i>, <i>segment_number</i>, <i>flight_date</i>)</li>
<li>The number of unique rows for the key (<i>flight_id</i>, <i>segment_number</i>)</li>
<li>The number of unique rows for the key (<i>flight_id</i>)</li>
</ul></p>
-<p>How does <ph conref="tunconrefs.dita#prod/productshortname"></ph> use these two numbers-the number of rows in
+<p>How does <ph conref="../conrefs.dita#prod/productshortname"></ph> use these two numbers-the number of rows in
a table and the cardinality of a particular key-to determine the selectivity
of a query? Take this example:
<codeblock><b>SELECT * FROM Flights, FlightAvailability
Modified: db/derby/docs/trunk/src/tuning/ctuntransform11313.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/tuning/ctuntransform11313.dita?view=diff&rev=524117&r1=524116&r2=524117
==============================================================================
--- db/derby/docs/trunk/src/tuning/ctuntransform11313.dita (original)
+++ db/derby/docs/trunk/src/tuning/ctuntransform11313.dita Fri Mar 30 08:14:48 2007
@@ -26,7 +26,7 @@
</metadata>
</prolog>
<conbody>
-<p>When <ph conref="tunconrefs.dita#prod/productshortname"></ph> evaluates a statement that references a view, it transforms
+<p>When <ph conref="../conrefs.dita#prod/productshortname"></ph> evaluates a statement that references a view, it transforms
the reference to a view into a derived table. It might make additional transformations
to improve performance.
</p>
Modified: db/derby/docs/trunk/src/tuning/ctuntransform13699.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/tuning/ctuntransform13699.dita?view=diff&rev=524117&r1=524116&r2=524117
==============================================================================
--- db/derby/docs/trunk/src/tuning/ctuntransform13699.dita (original)
+++ db/derby/docs/trunk/src/tuning/ctuntransform13699.dita Fri Mar 30 08:14:48 2007
@@ -27,7 +27,7 @@
</prolog>
<conbody>
<p>Subqueries are notoriously expensive to evaluate. This section describes
-some of the transformations that <ph conref="tunconrefs.dita#prod/productshortname"></ph> makes internally to reduce the
+some of the transformations that <ph conref="../conrefs.dita#prod/productshortname"></ph> makes internally to reduce the
cost of evaluating them.
</p>
</conbody></concept>
Modified: db/derby/docs/trunk/src/tuning/ctuntransform13966.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/tuning/ctuntransform13966.dita?view=diff&rev=524117&r1=524116&r2=524117
==============================================================================
--- db/derby/docs/trunk/src/tuning/ctuntransform13966.dita (original)
+++ db/derby/docs/trunk/src/tuning/ctuntransform13966.dita Fri Mar 30 08:14:48 2007
@@ -33,7 +33,7 @@
</metadata>
</prolog>
<conbody>
-<p>The <ph conref="tunconrefs.dita#prod/productshortname"></ph> SQL parser sometimes transforms SQL statements
+<p>The <ph conref="../conrefs.dita#prod/productshortname"></ph> SQL parser sometimes transforms SQL statements
internally for performance reasons. This appendix describes those transformations.
Understanding the internal language transformations can help you analyze and
tune performance. Understanding the internal language transformations is not
Modified: db/derby/docs/trunk/src/tuning/ctuntransform14044.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/tuning/ctuntransform14044.dita?view=diff&rev=524117&r1=524116&r2=524117
==============================================================================
--- db/derby/docs/trunk/src/tuning/ctuntransform14044.dita (original)
+++ db/derby/docs/trunk/src/tuning/ctuntransform14044.dita Fri Mar 30 08:14:48 2007
@@ -27,9 +27,9 @@
<conbody>
<p>Without a transformation, a statement that contains both ORDER BY and UNION
would require two separate sorting steps-one to satisfy ORDER BY and
-one to satisfy UNION (Currently <ph conref="tunconrefs.dita#prod/productshortname"></ph> uses sorting to eliminate duplicates
+one to satisfy UNION (Currently <ph conref="../conrefs.dita#prod/productshortname"></ph> uses sorting to eliminate duplicates
from a UNION. You can use UNION ALL to avoid sorting, but UNION ALL will return duplicates. So you only use UNION ALL to avoid sorting if you know that there are no duplicate rows in the tables).</p>
-<p>In some situations, <ph conref="tunconrefs.dita#prod/productshortname"></ph> can transform the statement internally
+<p>In some situations, <ph conref="../conrefs.dita#prod/productshortname"></ph> can transform the statement internally
into one that contains only one of these keywords (the ORDER BY is thrown
out). The requirements are:
<ul>
@@ -39,13 +39,13 @@
and they must be an in-order prefix of the columns in the target list of the
left side of the UNION. </li>
</ul></p>
-<p><ph conref="tunconrefs.dita#prod/productshortname"></ph> will be able to transform the following statements:
+<p><ph conref="../conrefs.dita#prod/productshortname"></ph> will be able to transform the following statements:
<codeblock><b>SELECT miles, meal
FROM Flights
UNION VALUES (1000, 'D')
ORDER BY 1
</b></codeblock></p>
-<p><ph conref="tunconrefs.dita#prod/productshortname"></ph> cannot avoid two sorting nodes in the following statement,
+<p><ph conref="../conrefs.dita#prod/productshortname"></ph> cannot avoid two sorting nodes in the following statement,
because of the order of the columns in the ORDER BY clause:
<codeblock><b>SELECT flight_id, segment_number FROM Flights
UNION
Modified: db/derby/docs/trunk/src/tuning/ctuntransform16033.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/tuning/ctuntransform16033.dita?view=diff&rev=524117&r1=524116&r2=524117
==============================================================================
--- db/derby/docs/trunk/src/tuning/ctuntransform16033.dita (original)
+++ db/derby/docs/trunk/src/tuning/ctuntransform16033.dita Fri Mar 30 08:14:48 2007
@@ -26,7 +26,7 @@
</metadata>
</prolog>
<conbody>
-<p>Sorting is an expensive process. <ph conref="tunconrefs.dita#prod/productshortname"></ph> tries to eliminate unnecessary
+<p>Sorting is an expensive process. <ph conref="../conrefs.dita#prod/productshortname"></ph> tries to eliminate unnecessary
sorting steps where possible.
</p>
</conbody></concept>
Modified: db/derby/docs/trunk/src/tuning/ctuntransform16279.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/tuning/ctuntransform16279.dita?view=diff&rev=524117&r1=524116&r2=524117
==============================================================================
--- db/derby/docs/trunk/src/tuning/ctuntransform16279.dita (original)
+++ db/derby/docs/trunk/src/tuning/ctuntransform16279.dita Fri Mar 30 08:14:48 2007
@@ -27,7 +27,7 @@
<p>A DISTINCT (and the corresponding sort) can be eliminated from a query
if a uniqueness condition exists that ensures that no duplicate values will
be returned. If no duplicate values are returned, the DISTINCT node is superfluous,
-and <ph conref="tunconrefs.dita#prod/productshortname"></ph> transforms the
+and <ph conref="../conrefs.dita#prod/productshortname"></ph> transforms the
statement internally into one without the DISTINCT keyword.</p>
<p>The requirements are: <ul>
<li>No GROUP BY list. </li>
Modified: db/derby/docs/trunk/src/tuning/ctuntransform21780.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/tuning/ctuntransform21780.dita?view=diff&rev=524117&r1=524116&r2=524117
==============================================================================
--- db/derby/docs/trunk/src/tuning/ctuntransform21780.dita (original)
+++ db/derby/docs/trunk/src/tuning/ctuntransform21780.dita Fri Mar 30 08:14:48 2007
@@ -27,8 +27,8 @@
<conbody>
<p>Without a transformation, a statement that contains both DISTINCT and ORDER
BY would require two separate sorting steps-one to satisfy DISTINCT
-and one to satisfy ORDER BY. (Currently, <ph conref="tunconrefs.dita#prod/productshortname"></ph> uses sorting to evaluate
-DISTINCT. There are, in theory, other ways to accomplish this.) In some situations, <ph conref="tunconrefs.dita#prod/productshortname"></ph> can
+and one to satisfy ORDER BY. (Currently, <ph conref="../conrefs.dita#prod/productshortname"></ph> uses sorting to evaluate
+DISTINCT. There are, in theory, other ways to accomplish this.) In some situations, <ph conref="../conrefs.dita#prod/productshortname"></ph> can
transform the statement internally into one that contains only one of these
keywords. The requirements are:
<ul>
@@ -44,5 +44,5 @@
<p>is transformed into
<codeblock><b>SELECT DISTINCT miles, meal
FROM Flights</b></codeblock>Note that these are not equivalent functions; this
-is simply an internal <ph conref="tunconrefs.dita#prod/productshortname"></ph> transformation.</p>
+is simply an internal <ph conref="../conrefs.dita#prod/productshortname"></ph> transformation.</p>
</conbody></concept>
Modified: db/derby/docs/trunk/src/tuning/ctuntransform22576.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/tuning/ctuntransform22576.dita?view=diff&rev=524117&r1=524116&r2=524117
==============================================================================
--- db/derby/docs/trunk/src/tuning/ctuntransform22576.dita (original)
+++ db/derby/docs/trunk/src/tuning/ctuntransform22576.dita Fri Mar 30 08:14:48 2007
@@ -25,7 +25,7 @@
</metadata>
</prolog>
<conbody>
-<p>When evaluating a statement that references a view, <ph conref="tunconrefs.dita#prod/productshortname"></ph> internally
+<p>When evaluating a statement that references a view, <ph conref="../conrefs.dita#prod/productshortname"></ph> internally
transforms a view into a derived table. This derived table might also be a
candidate for <i>flattening</i> into the outer query block.</p>
<p>A view or derived table can be flattened into the outer query block if
Modified: db/derby/docs/trunk/src/tuning/ctuntransform25857.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/tuning/ctuntransform25857.dita?view=diff&rev=524117&r1=524116&r2=524117
==============================================================================
--- db/derby/docs/trunk/src/tuning/ctuntransform25857.dita (original)
+++ db/derby/docs/trunk/src/tuning/ctuntransform25857.dita Fri Mar 30 08:14:48 2007
@@ -36,7 +36,7 @@
of subquery must return only one row. If evaluating the subquery causes a
cardinality violation (if it returns more than one row), an exception is thrown
when the subquery is run. </p><p>Subquery materialization is detected before
-optimization, which allows the <ph conref="tunconrefs.dita#prod/productshortname"></ph> optimizer
+optimization, which allows the <ph conref="../conrefs.dita#prod/productshortname"></ph> optimizer
to see a materialized subquery as an unknown constant value. The comparison
is therefore optimizable. </p><p>The original statement is transformed into
the following two statements: <codeblock><b><i>constant</i></b> = SELECT MAX(manager) FROM Org
@@ -51,14 +51,14 @@
WHERE t1.i = x1.a AND t1.i in (1, 3, 5, 7) </codeblock>In this example, the
subquery x1 is noncorrelated because it does not reference any of the columns
from the outer query. The subquery is nonflattenable because of the DISTINCT
-keyword. <ph conref="tunconrefs.dita#prod/productshortname"></ph> does not
+keyword. <ph conref="../conrefs.dita#prod/productshortname"></ph> does not
flatten DISTINCT subqueries. This subquery is eligible for materialization.
Since there is an equijoin predicate between the subquery x1 and the table
-t1 (namely, t1.i = x1.a), the <ph conref="tunconrefs.dita#prod/productshortname"></ph> optimizer
+t1 (namely, t1.i = x1.a), the <ph conref="../conrefs.dita#prod/productshortname"></ph> optimizer
will consider performing a hash join between t1 and x1 (with x1 as the inner
-operand). If that approach yields the best cost, <ph conref="tunconrefs.dita#prod/productshortname"></ph> materializes
+operand). If that approach yields the best cost, <ph conref="../conrefs.dita#prod/productshortname"></ph> materializes
the subquery x1 to perform the hash join. The subquery is evaluated only a
-single time and the results are stored in an in-memory hash table. <ph conref="tunconrefs.dita#prod/productshortname"></ph> then
+single time and the results are stored in an in-memory hash table. <ph conref="../conrefs.dita#prod/productshortname"></ph> then
executes the join using the in-memory result set for x1.</p></section>
</conbody>
</concept>
Modified: db/derby/docs/trunk/src/tuning/ctuntransform25868.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/tuning/ctuntransform25868.dita?view=diff&rev=524117&r1=524116&r2=524117
==============================================================================
--- db/derby/docs/trunk/src/tuning/ctuntransform25868.dita (original)
+++ db/derby/docs/trunk/src/tuning/ctuntransform25868.dita Fri Mar 30 08:14:48 2007
@@ -28,7 +28,7 @@
<conbody>
<p>An EXISTS join is a join in which the right side of the join needs to be
probed only once for each outer row. Using such a definition, an EXISTS join
-does not literally use the EXISTS keyword. <ph conref="tunconrefs.dita#prod/productshortname"></ph> treats a statement
+does not literally use the EXISTS keyword. <ph conref="../conrefs.dita#prod/productshortname"></ph> treats a statement
as an EXISTS join when there will be at most one matching row from the right
side of the join for a given row in the outer table.</p>
<p>A subquery that cannot be flattened into a normal join because of a uniqueness
@@ -37,8 +37,8 @@
<codeblock><b>SELECT c1 FROM t1 WHERE c1 IN (SELECT c1 FROM t2)</b></codeblock>
<p>This query could not be flattened into a normal join because such a join
would return the wrong results. However, this query can be flattened into
-a join recognized internally by the <ph conref="tunconrefs.dita#prod/productshortname"></ph> system as an EXISTS join.
-When processing an EXISTS join, <ph conref="tunconrefs.dita#prod/productshortname"></ph> knows to stop processing the right
+a join recognized internally by the <ph conref="../conrefs.dita#prod/productshortname"></ph> system as an EXISTS join.
+When processing an EXISTS join, <ph conref="../conrefs.dita#prod/productshortname"></ph> knows to stop processing the right
side of the join after a single row is returned. The transformed statement
would look something like this:
<codeblock><b>SELECT c1 FROM t1, t2
Modified: db/derby/docs/trunk/src/tuning/ctuntransform35783.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/tuning/ctuntransform35783.dita?view=diff&rev=524117&r1=524116&r2=524117
==============================================================================
--- db/derby/docs/trunk/src/tuning/ctuntransform35783.dita (original)
+++ db/derby/docs/trunk/src/tuning/ctuntransform35783.dita Fri Mar 30 08:14:48 2007
@@ -37,9 +37,9 @@
<note>In a few
cases, a WHERE clause with predicates joined by OR can be transformed into
an optimizable statement. See <xref href="rtuntransform590.dita#rtuntransform590"/>.</note></p>
-<p><ph conref="tunconrefs.dita#prod/productshortname"></ph> can transform some predicates internally so that at least one
+<p><ph conref="../conrefs.dita#prod/productshortname"></ph> can transform some predicates internally so that at least one
of the predicates is optimizable and thus the statement is optimizable. This
-section describes the predicate transformations that <ph conref="tunconrefs.dita#prod/productshortname"></ph> performs
+section describes the predicate transformations that <ph conref="../conrefs.dita#prod/productshortname"></ph> performs
to make predicates optimizable.</p>
<p>A predicate that uses the following comparison operators can sometimes
be transformed internally into optimizable predicates.
Modified: db/derby/docs/trunk/src/tuning/ctuntransform36368.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/tuning/ctuntransform36368.dita?view=diff&rev=524117&r1=524116&r2=524117
==============================================================================
--- db/derby/docs/trunk/src/tuning/ctuntransform36368.dita (original)
+++ db/derby/docs/trunk/src/tuning/ctuntransform36368.dita Fri Mar 30 08:14:48 2007
@@ -26,7 +26,7 @@
</prolog>
<conbody>
<p>Subqueries are allowed to return more than one row when used with IN, EXISTS,
-and ANY. However, for each row returned in the outer row, <ph conref="tunconrefs.dita#prod/productshortname"></ph> evaluates
+and ANY. However, for each row returned in the outer row, <ph conref="../conrefs.dita#prod/productshortname"></ph> evaluates
the subquery until it returns one row; it does not evaluate the subquery for
all rows returned.</p>
<p>For example, given two tables, <i>t1</i> and <i>t2</i>:
Modified: db/derby/docs/trunk/src/tuning/ctuntransform36623.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/tuning/ctuntransform36623.dita?view=diff&rev=524117&r1=524116&r2=524117
==============================================================================
--- db/derby/docs/trunk/src/tuning/ctuntransform36623.dita (original)
+++ db/derby/docs/trunk/src/tuning/ctuntransform36623.dita Fri Mar 30 08:14:48 2007
@@ -34,7 +34,7 @@
<codeblock>SELECT *
FROM v2
WHERE a = 'LUCCHESSI'</codeblock></p>
-<p>When <ph conref="tunconrefs.dita#prod/productshortname"></ph> transforms
+<p>When <ph conref="../conrefs.dita#prod/productshortname"></ph> transforms
that statement by first transforming the view into a derived table, it places
the predicate at the top level of the new query, outside the scope of the
derived table: <codeblock>SELECT a, b
@@ -45,14 +45,14 @@
v1(a, b)
</codeblock></p>
<p>In the example in the preceding section (see <xref href="ctuntransform22576.dita#ctuntransform22576"></xref>), <ph
-conref="tunconrefs.dita#prod/productshortname"></ph> was able to flatten the
+conref="../conrefs.dita#prod/productshortname"></ph> was able to flatten the
derived table into the main SELECT, so the predicate in the outer SELECT could
be evaluated at a useful point in the query. This is not possible in this
example, because the underlying view does not satisfy all the requirements
of view flattening.</p>
<p>However, if the source of all of the column references in a predicate is
a <xref href="ctuntransform13966.dita#ctuntransform13966/rtuntransform13785">simple
-column reference</xref> in the underlying view or table, <ph conref="tunconrefs.dita#prod/productshortname"></ph> is
+column reference</xref> in the underlying view or table, <ph conref="../conrefs.dita#prod/productshortname"></ph> is
able to <i>push</i> the predicate <i>down</i> to the underlying view. Pushing
down means that the qualification described by the predicate can be evaluated
when the view is being evaluated. In our example, the column reference in
@@ -63,9 +63,9 @@
FROM (SELECT sales_person, MAX(sales) from Sales
WHERE sales_person = 'LUCCHESSI'
GROUP BY sales_person) v1(a, b)</codeblock></p>
-<p>Without the transformation, <ph conref="tunconrefs.dita#prod/productshortname"></ph> would
+<p>Without the transformation, <ph conref="../conrefs.dita#prod/productshortname"></ph> would
have to scan the entire table <i>t1</i> to form all the groups, only to throw
-out all but one of the groups. With the transformation, <ph conref="tunconrefs.dita#prod/productshortname"></ph> is
+out all but one of the groups. With the transformation, <ph conref="../conrefs.dita#prod/productshortname"></ph> is
able to make that qualification part of the derived table.</p>
<p>If there were a predicate that referenced column <i>b</i>, it could not
be pushed down, because in the underlying view, column <i>b</i> is not a <xref
Modified: db/derby/docs/trunk/src/tuning/ctuntransform37032.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/tuning/ctuntransform37032.dita?view=diff&rev=524117&r1=524116&r2=524117
==============================================================================
--- db/derby/docs/trunk/src/tuning/ctuntransform37032.dita (original)
+++ db/derby/docs/trunk/src/tuning/ctuntransform37032.dita Fri Mar 30 08:14:48 2007
@@ -28,7 +28,7 @@
<conbody>
<p>The transitive property of numbers states that if A = B and B = C, then
A = C.</p>
-<p><ph conref="tunconrefs.dita#prod/productshortname"></ph> applies this property to query predicates to add additional
+<p><ph conref="../conrefs.dita#prod/productshortname"></ph> applies this property to query predicates to add additional
predicates to the query in order to give the optimizer more information. This
process is called <i>transitive closure</i>. There are two
types of transitive closure:
Modified: db/derby/docs/trunk/src/tuning/ctuntransform47182.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/tuning/ctuntransform47182.dita?view=diff&rev=524117&r1=524116&r2=524117
==============================================================================
--- db/derby/docs/trunk/src/tuning/ctuntransform47182.dita (original)
+++ db/derby/docs/trunk/src/tuning/ctuntransform47182.dita Fri Mar 30 08:14:48 2007
@@ -21,5 +21,5 @@
<prolog>
</prolog>
<conbody>
-<p><ph conref="tunconrefs.dita#prod/productshortname"></ph> flattens VALUES subqueries to improve performance.</p>
+<p><ph conref="../conrefs.dita#prod/productshortname"></ph> flattens VALUES subqueries to improve performance.</p>
</conbody></concept>
Modified: db/derby/docs/trunk/src/tuning/ctuntransform55045.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/tuning/ctuntransform55045.dita?view=diff&rev=524117&r1=524116&r2=524117
==============================================================================
--- db/derby/docs/trunk/src/tuning/ctuntransform55045.dita (original)
+++ db/derby/docs/trunk/src/tuning/ctuntransform55045.dita Fri Mar 30 08:14:48 2007
@@ -21,7 +21,7 @@
<prolog>
</prolog>
<conbody>
-<p><ph conref="tunconrefs.dita#prod/productshortname"></ph> transforms OUTER to INNER joins when the predicate filters
+<p><ph conref="../conrefs.dita#prod/productshortname"></ph> transforms OUTER to INNER joins when the predicate filters
out all nulls on the join column. This transformation can allow more potential
query plans and thus better performance.</p>
</conbody></concept>
Modified: db/derby/docs/trunk/src/tuning/rtunoptimz1004602.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/tuning/rtunoptimz1004602.dita?view=diff&rev=524117&r1=524116&r2=524117
==============================================================================
--- db/derby/docs/trunk/src/tuning/rtunoptimz1004602.dita (original)
+++ db/derby/docs/trunk/src/tuning/rtunoptimz1004602.dita Fri Mar 30 08:14:48 2007
@@ -23,26 +23,26 @@
<refbody>
<section><p>The following queries do <i>not</i> provide start and
stop conditions for a scan of <i>OrigIndex</i>, the index
-on the <i>orig_airport</i> column in <i>Flights.</i> However, some of these queries allow <ph conref="tunconrefs.dita#prod/productshortname"></ph> to do an index
+on the <i>orig_airport</i> column in <i>Flights.</i> However, some of these queries allow <ph conref="../conrefs.dita#prod/productshortname"></ph> to do an index
rather than a table scan because the index covers the query.
-<codeblock><b><ph>-- <ph conref="tunconrefs.dita#prod/productshortname"></ph> would scan entire table; comparison is not with a
+<codeblock><b><ph>-- <ph conref="../conrefs.dita#prod/productshortname"></ph> would scan entire table; comparison is not with a
-- constant or with a column in another table</ph>
SELECT *
FROM Flights
WHERE orig_airport = dest_airport
-<ph>-- <ph conref="tunconrefs.dita#prod/productshortname"></ph> would scan entire table; <> operator is not optimizable</ph>
+<ph>-- <ph conref="../conrefs.dita#prod/productshortname"></ph> would scan entire table; <> operator is not optimizable</ph>
SELECT *
FROM Flights
WHERE orig_airport <> 'SFO'
<ph>-- not valid operator for matching index scan
--- However, <ph conref="tunconrefs.dita#prod/productshortname"></ph> would do an index
+-- However, <ph conref="../conrefs.dita#prod/productshortname"></ph> would do an index
-- rather than a table scan because
-- index covers query</ph>
SELECT orig_airport
FROM Flights
WHERE orig_airport <> 'SFO'
<ph>-- use of a function is not simple column reference
--- <ph conref="tunconrefs.dita#prod/productshortname"></ph> would scan entire index, but not table
+-- <ph conref="../conrefs.dita#prod/productshortname"></ph> would scan entire index, but not table
-- (index covers query)</ph>
SELECT orig_airport
FROM Flights
Modified: db/derby/docs/trunk/src/tuning/rtunoptimz1004810.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/tuning/rtunoptimz1004810.dita?view=diff&rev=524117&r1=524116&r2=524117
==============================================================================
--- db/derby/docs/trunk/src/tuning/rtunoptimz1004810.dita (original)
+++ db/derby/docs/trunk/src/tuning/rtunoptimz1004810.dita Fri Mar 30 08:14:48 2007
@@ -44,7 +44,7 @@
SELECT *
FROM Flights
WHERE segment_number = 2
-<ph>-- <ph conref="tunconrefs.dita#prod/productshortname"></ph> would scan entire table; comparison of first column
+<ph>-- <ph conref="../conrefs.dita#prod/productshortname"></ph> would scan entire table; comparison of first column
-- is not with a constant or column in another table
-- and no covering index applies</ph>
SELECT *
Modified: db/derby/docs/trunk/src/tuning/rtunproper10607.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/tuning/rtunproper10607.dita?view=diff&rev=524117&r1=524116&r2=524117
==============================================================================
--- db/derby/docs/trunk/src/tuning/rtunproper10607.dita (original)
+++ db/derby/docs/trunk/src/tuning/rtunproper10607.dita Fri Mar 30 08:14:48 2007
@@ -24,15 +24,15 @@
</metadata>
</prolog><refbody>
<section><title>Function</title>
-<p>Determines the number of seconds after which <ph conref="tunconrefs.dita#prod/productshortname"></ph> checks whether
+<p>Determines the number of seconds after which <ph conref="../conrefs.dita#prod/productshortname"></ph> checks whether
a transaction waiting to obtain a lock is involved in a deadlock. If a deadlock
-has occurred, and <ph conref="tunconrefs.dita#prod/productshortname"></ph> chooses the transaction as a deadlock victim, <ph conref="tunconrefs.dita#prod/productshortname"></ph> aborts
+has occurred, and <ph conref="../conrefs.dita#prod/productshortname"></ph> chooses the transaction as a deadlock victim, <ph conref="../conrefs.dita#prod/productshortname"></ph> aborts
the transaction. The transaction receives an <i>SQLException</i> of <i>SQLState</i> 40001. If the transaction is not
chosen as the victim, it continues to wait for a lock if <i><xref href="rtunproper46141.dita#rtunproper46141">derby.locks.waitTimeout</xref></i> is set to a higher value than the
value of <i>derby.locks.deadlockTimeout</i>.</p>
<p>If this property is set to a higher value than <i><xref href="rtunproper46141.dita#rtunproper46141">derby.locks.waitTimeout</xref>,</i> no deadlock checking occurs. See <i><xref href="rtunproper46141.dita#rtunproper46141">derby.locks.waitTimeout</xref>.</i></p>
<p>For more information about deadlock checking, see "Deadlocks" in
-Chapter 5 of the <cite><ph conref="tunconrefs.dita#pub/citdevelop"></ph></cite>.</p>
+Chapter 5 of the <cite><ph conref="../conrefs.dita#pub/citdevelop"></ph></cite>.</p>
</section>
<section><title>Default</title>
<p id="rtunproper29374">20 seconds.</p>
Modified: db/derby/docs/trunk/src/tuning/rtunproper13217.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/tuning/rtunproper13217.dita?view=diff&rev=524117&r1=524116&r2=524117
==============================================================================
--- db/derby/docs/trunk/src/tuning/rtunproper13217.dita (original)
+++ db/derby/docs/trunk/src/tuning/rtunproper13217.dita Fri Mar 30 08:14:48 2007
@@ -24,8 +24,8 @@
</metadata>
</prolog><refbody>
<section><title>Function</title>
-<p>Specifies whether to append to or overwrite (delete and recreate) the <i>derby.log</i> file when the <ph conref="tunconrefs.dita#prod/productshortname"></ph> engine is started. The <i>derby.log</i> file is used to record errors and other information. This information can be important when debugging problems within a system.</p>
-<p>You can set this property even if the file does not yet exist; <ph conref="tunconrefs.dita#prod/productshortname"></ph> creates
+<p>Specifies whether to append to or overwrite (delete and recreate) the <i>derby.log</i> file when the <ph conref="../conrefs.dita#prod/productshortname"></ph> engine is started. The <i>derby.log</i> file is used to record errors and other information. This information can be important when debugging problems within a system.</p>
+<p>You can set this property even if the file does not yet exist; <ph conref="../conrefs.dita#prod/productshortname"></ph> creates
the file.</p>
</section>
<section><title>Default</title>
@@ -39,6 +39,6 @@
<p><xref href="ctunproper51399.dita#ctunproper51399/rtunproper41229">system-wide</xref></p>
</section>
<section><title>Dynamic or static</title>
-<p>This property is static; if you change it while <ph conref="tunconrefs.dita#prod/productshortname"></ph> is running,
+<p>This property is static; if you change it while <ph conref="../conrefs.dita#prod/productshortname"></ph> is running,
the change does not take effect until you reboot.</p>
</section></refbody></reference>
Modified: db/derby/docs/trunk/src/tuning/rtunproper13766.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/tuning/rtunproper13766.dita?view=diff&rev=524117&r1=524116&r2=524117
==============================================================================
--- db/derby/docs/trunk/src/tuning/rtunproper13766.dita (original)
+++ db/derby/docs/trunk/src/tuning/rtunproper13766.dita Fri Mar 30 08:14:48 2007
@@ -26,10 +26,10 @@
</metadata></prolog>
<refbody>
<section><title>Function</title> <p>Specifies the authentication provider
-for <ph conref="tunconrefs.dita#prod/productshortname"></ph> user authentication. </p> <p>Legal
+for <ph conref="../conrefs.dita#prod/productshortname"></ph> user authentication. </p> <p>Legal
values include: <ul>
<li>LDAP <p>An external LDAP directory service.</p></li>
-<li>BUILTIN <p><ph conref="tunconrefs.dita#prod/productshortname"></ph>'s
+<li>BUILTIN <p><ph conref="../conrefs.dita#prod/productshortname"></ph>'s
simple internal user authentication repository.</p></li>
<li>a complete Java class name <p>A user-defined class that provides user
authentication.</p></li>
@@ -45,14 +45,14 @@
</ul></p> <p>Alternatively, you can write your own class to provide a different
external authentication service. This class must implement the public interface <i>org.apache.derby.authentication.UserAuthenticator </i>and
throw exceptions of the type <i>java.sql.SQLException</i> where appropriate.
-Using a user-defined class makes <ph conref="tunconrefs.dita#prod/productshortname"></ph> adaptable
+Using a user-defined class makes <ph conref="../conrefs.dita#prod/productshortname"></ph> adaptable
to various naming and directory services. For example, the class could allow <ph
-conref="tunconrefs.dita#prod/productshortname"></ph> to hook up to an existing
+conref="../conrefs.dita#prod/productshortname"></ph> to hook up to an existing
user authentication service that uses any of the standard directory and naming
-service providers to JNDI. </p> <p>To enable any <ph conref="tunconrefs.dita#prod/productshortname"></ph> user
+service providers to JNDI. </p> <p>To enable any <ph conref="../conrefs.dita#prod/productshortname"></ph> user
authentication, you must set the <i><xref href="rtunproper27467.dita#rtunproper27467">derby.connection.requireAuthentication</xref></i> property
to true.</p> <p>For more information about user authentication, see the <cite><ph
-conref="tunconrefs.dita#pub/citdevelop"></ph>.</cite></p> </section>
+conref="../conrefs.dita#pub/citdevelop"></ph>.</cite></p> </section>
<refsyn><title>Syntax</title> <codeblock><b>derby.authentication.provider={ LDAP | BUILTIN | <b><i>classProviderName</i></b> }</b></codeblock> </refsyn>
<section><title>Default</title> <p>BUILTIN</p> </section>
<example><title>Example</title> <codeblock><b><ph>-- system-wide property</ph>
@@ -62,7 +62,7 @@
'derby.authentication.provider',
'BUILTIN')</b></codeblock> </example>
<section><title>Dynamic or static</title> <p>Static. For system-wide properties,
-you must reboot <ph conref="tunconrefs.dita#prod/productshortname"></ph> for
+you must reboot <ph conref="../conrefs.dita#prod/productshortname"></ph> for
the change to take effect. For database-wide properties, you must reboot the
database for the change to take effect.</p> </section>
</refbody>
Modified: db/derby/docs/trunk/src/tuning/rtunproper18151.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/tuning/rtunproper18151.dita?view=diff&rev=524117&r1=524116&r2=524117
==============================================================================
--- db/derby/docs/trunk/src/tuning/rtunproper18151.dita (original)
+++ db/derby/docs/trunk/src/tuning/rtunproper18151.dita Fri Mar 30 08:14:48 2007
@@ -36,6 +36,6 @@
<codeblock><b>derby.stream.error.file=error.txt</b></codeblock>
</example>
<section><title>Dynamic or static</title>
-<p>This property is static; if you change it while <ph conref="tunconrefs.dita#prod/productshortname"></ph> is running,
+<p>This property is static; if you change it while <ph conref="../conrefs.dita#prod/productshortname"></ph> is running,
the change does not take effect until you reboot.</p>
</section></refbody></reference>
Modified: db/derby/docs/trunk/src/tuning/rtunproper23835.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/tuning/rtunproper23835.dita?view=diff&rev=524117&r1=524116&r2=524117
==============================================================================
--- db/derby/docs/trunk/src/tuning/rtunproper23835.dita (original)
+++ db/derby/docs/trunk/src/tuning/rtunproper23835.dita Fri Mar 30 08:14:48 2007
@@ -25,8 +25,8 @@
</prolog><refbody>
<section><title>Function</title>
<p>Causes a detailed list of locks at the time of a deadlock or a timeout
-to be written to the error log (typically the <i>derby.log</i>). For a deadlock, <ph conref="tunconrefs.dita#prod/productshortname"></ph> will describe the cycle of locks which caused
-the deadlock. For a timeout, <ph conref="tunconrefs.dita#prod/productshortname"></ph> will print the entire lock list at the
+to be written to the error log (typically the <i>derby.log</i>). For a deadlock, <ph conref="../conrefs.dita#prod/productshortname"></ph> will describe the cycle of locks which caused
+the deadlock. For a timeout, <ph conref="../conrefs.dita#prod/productshortname"></ph> will print the entire lock list at the
time of the timeout. This property is meaningful only if the <i><xref href="rtunproper98166.dita#rtunproper98166">derby.locks.monitor</xref></i> property is set to <i>true</i>.
<note>This level of debugging is intrusive: it can alter
the timing of the application, reduce performance severely, and produce a
Modified: db/derby/docs/trunk/src/tuning/rtunproper24390.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/tuning/rtunproper24390.dita?view=diff&rev=524117&r1=524116&r2=524117
==============================================================================
--- db/derby/docs/trunk/src/tuning/rtunproper24390.dita (original)
+++ db/derby/docs/trunk/src/tuning/rtunproper24390.dita Fri Mar 30 08:14:48 2007
@@ -42,7 +42,7 @@
'derby.database.propertiesOnly','true')</b></codeblock>
</example>
<section><title>Dynamic or static</title>
-<p>This property is dynamic; if you change it while <ph conref="tunconrefs.dita#prod/productshortname"></ph> is running,
+<p>This property is dynamic; if you change it while <ph conref="../conrefs.dita#prod/productshortname"></ph> is running,
the change takes effect immediately. For information about dynamic changes
to properties, see <xref href="ctunsetprop44147.dita#ctunsetprop44147"/>.</p>
</section></refbody></reference>
Modified: db/derby/docs/trunk/src/tuning/rtunproper24846.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/tuning/rtunproper24846.dita?view=diff&rev=524117&r1=524116&r2=524117
==============================================================================
--- db/derby/docs/trunk/src/tuning/rtunproper24846.dita (original)
+++ db/derby/docs/trunk/src/tuning/rtunproper24846.dita Fri Mar 30 08:14:48 2007
@@ -41,7 +41,7 @@
(or even accessed) using this property. If you set this property to <i>noAccess</i> or <i>readOnlyAccess</i>, be sure to allow
at least one user full access. See <i><xref href="rtunproper25025.dita#rtunproper25025"/></i> and <i><xref href="rtunproper39325.dita#rtunproper39325"/>.</i></note></p>
<p>For more information about user authorization, see "User Authorization"
-in Chapter 7 of the <cite><ph conref="tunconrefs.dita#pub/citdevelop"></ph></cite>.
+in Chapter 7 of the <cite><ph conref="../conrefs.dita#pub/citdevelop"></ph></cite>.
<codeblock><b>CALL SYSCS_UTIL.SYSCS_SET_DATABASE_PROPERTY(
'derby.database.defaultConnectionMode',
'{ noAccess | readOnlyAccess | fullAccess}')</b></codeblock></p>
Modified: db/derby/docs/trunk/src/tuning/rtunproper25025.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/tuning/rtunproper25025.dita?view=diff&rev=524117&r1=524116&r2=524117
==============================================================================
--- db/derby/docs/trunk/src/tuning/rtunproper25025.dita (original)
+++ db/derby/docs/trunk/src/tuning/rtunproper25025.dita Fri Mar 30 08:14:48 2007
@@ -36,7 +36,7 @@
follow the rules of <i>SQL92Identifiers</i> and can be delimited.
Specifying a user name that does not follow these rules raises an exception.</note></p>
<p>For more information about user authorization, see "User Authorization"
-in Chapter 7 of the <cite><ph conref="tunconrefs.dita#pub/citdevelop"></ph></cite>.</p>
+in Chapter 7 of the <cite><ph conref="../conrefs.dita#pub/citdevelop"></ph></cite>.</p>
</section>
<refsyn><title>Syntax</title>
<codeblock><b><ph>-- database-level property</ph>
Modified: db/derby/docs/trunk/src/tuning/rtunproper25581.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/tuning/rtunproper25581.dita?view=diff&rev=524117&r1=524116&r2=524117
==============================================================================
--- db/derby/docs/trunk/src/tuning/rtunproper25581.dita (original)
+++ db/derby/docs/trunk/src/tuning/rtunproper25581.dita Fri Mar 30 08:14:48 2007
@@ -26,11 +26,11 @@
</metadata></prolog>
<refbody>
<section><title>Function</title> <p>Specifies the location of the external
-directory service that provides user authentication for the <ph conref="tunconrefs.dita#prod/productshortname"></ph> system
+directory service that provides user authentication for the <ph conref="../conrefs.dita#prod/productshortname"></ph> system
as defined with <i><xref href="rtunproper13766.dita#rtunproper13766">derby.authentication.provider</xref>.</i> For
LDAP, specify the host name and port number.</p> <p>The server must be known
on the network.</p> <p>For more information about external user authentication,
-see "External Directory Service" in the <cite><ph conref="tunconrefs.dita#pub/citdevelop"></ph>.</cite></p> </section>
+see "External Directory Service" in the <cite><ph conref="../conrefs.dita#pub/citdevelop"></ph>.</cite></p> </section>
<section><title>Default</title> <p>Not applicable. Note that if the protocol type
is unspecified, it defaults to LDAP.</p> </section>
<refsyn><title>Syntax</title> <codeblock><b>derby.authentication.server=
@@ -55,7 +55,7 @@
'derby.authentication.server',
'godfrey:9090')</b></codeblock> </example>
<section><title>Dynamic or static</title> <p>Static. For system-wide properties,
-you must reboot <ph conref="tunconrefs.dita#prod/productshortname"></ph> for
+you must reboot <ph conref="../conrefs.dita#prod/productshortname"></ph> for
the change to take effect. For database-wide properties, you must reboot the
database for the change to take effect.</p> </section>
</refbody>
Modified: db/derby/docs/trunk/src/tuning/rtunproper26978.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/tuning/rtunproper26978.dita?view=diff&rev=524117&r1=524116&r2=524117
==============================================================================
--- db/derby/docs/trunk/src/tuning/rtunproper26978.dita (original)
+++ db/derby/docs/trunk/src/tuning/rtunproper26978.dita Fri Mar 30 08:14:48 2007
@@ -29,7 +29,7 @@
<codeblock><b>ou=people,o=ExampleSite.com</b></codeblock></p>
<p>When using Netscape Directory Server, set this property to the root DN,
the special entry to which access control does not apply.</p>
-<p>For more information about LDAP user authentication, see the <cite><ph conref="tunconrefs.dita#pub/citdevelop"></ph>.</cite></p>
+<p>For more information about LDAP user authentication, see the <cite><ph conref="../conrefs.dita#pub/citdevelop"></ph>.</cite></p>
</section>
<example><title>Example</title>
<codeblock><b><ph>-- system-wide property</ph>
@@ -41,7 +41,7 @@
'ou=people,o=ExampleSite.com')</b></codeblock>
</example>
<section><title>Dynamic or static</title>
-<p>Static. For system-wide properties, you must reboot <ph conref="tunconrefs.dita#prod/productshortname"></ph> for the
+<p>Static. For system-wide properties, you must reboot <ph conref="../conrefs.dita#prod/productshortname"></ph> for the
change to take effect. For database-wide properties, you must reboot the database
for the change to take effect.</p>
</section></refbody></reference>
Modified: db/derby/docs/trunk/src/tuning/rtunproper26985.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/tuning/rtunproper26985.dita?view=diff&rev=524117&r1=524116&r2=524117
==============================================================================
--- db/derby/docs/trunk/src/tuning/rtunproper26985.dita (original)
+++ db/derby/docs/trunk/src/tuning/rtunproper26985.dita Fri Mar 30 08:14:48 2007
@@ -25,11 +25,11 @@
</metadata>
</prolog><refbody>
<section><title>Function</title>
-<p>Specifies which errors are logged to the <ph conref="tunconrefs.dita#prod/productshortname"></ph> error log (typically
+<p>Specifies which errors are logged to the <ph conref="../conrefs.dita#prod/productshortname"></ph> error log (typically
the <i>derby.log</i> file). In test environments, use the
setting <i>derby.stream.error.logSeverityLevel=0</i> so that
all problems are reported.</p>
-<p>Any error raised in a <ph conref="tunconrefs.dita#prod/productshortname"></ph> system is given a level of severity.
+<p>Any error raised in a <ph conref="../conrefs.dita#prod/productshortname"></ph> system is given a level of severity.
This property indicates the minimum severity necessary for an error to appear
in the error log. The severities are defined in the class <i>org.apache.derby.types.ExceptionSeverity</i>. The higher the number, the more severe the error.
<ul>
@@ -43,7 +43,7 @@
<p>Errors that cause the connection to
be closed.</p></li>
<li><i>50000</i>
-<p>Errors that shut down the <ph conref="tunconrefs.dita#prod/productshortname"></ph> system.</p></li>
+<p>Errors that shut down the <ph conref="../conrefs.dita#prod/productshortname"></ph> system.</p></li>
</ul></p>
</section>
<section><title>Default</title>
@@ -54,6 +54,6 @@
derby.stream.error.logSeverityLevel=30000</b></codeblock>
</example>
<section><title>Dynamic or static</title>
-<p>This property is static; if you change it while <ph conref="tunconrefs.dita#prod/productshortname"></ph> is running,
+<p>This property is static; if you change it while <ph conref="../conrefs.dita#prod/productshortname"></ph> is running,
the change does not take effect until you reboot.</p>
</section></refbody></reference>
Modified: db/derby/docs/trunk/src/tuning/rtunproper27355.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/tuning/rtunproper27355.dita?view=diff&rev=524117&r1=524116&r2=524117
==============================================================================
--- db/derby/docs/trunk/src/tuning/rtunproper27355.dita (original)
+++ db/derby/docs/trunk/src/tuning/rtunproper27355.dita Fri Mar 30 08:14:48 2007
@@ -33,10 +33,10 @@
set to <i>derby.user</i>.</li>
</ul></p> </section>
<section><title>Users and Passwords</title> <p>This property creates valid
-clear-text users and passwords within <ph conref="tunconrefs.dita#prod/productshortname"></ph> when
+clear-text users and passwords within <ph conref="../conrefs.dita#prod/productshortname"></ph> when
the <i><xref href="rtunproper13766.dita#rtunproper13766">derby.authentication.provider</xref></i> property
is set to <i>BUILTIN</i>. For information about users, see "Working with User
-Authentication" in the <cite><ph conref="tunconrefs.dita#pub/citdevelop"></ph></cite>.
+Authentication" in the <cite><ph conref="../conrefs.dita#pub/citdevelop"></ph></cite>.
<ul>
<li><i>Database-Level Properties</i> <p>When you create users with database-level
properties, those users are available to the specified database only.</p> <p>You
@@ -48,7 +48,7 @@
set it several times. To delete a user, remove that user from the file.</p> <p>You
can define this property in the usual ways-typically in the <i>derby.properties</i> file.</p></li>
</ul></p> <p>When a user name and its corresponding password are provided
-in the <i>DriverManager.getConnection</i> call, <ph conref="tunconrefs.dita#prod/productshortname"></ph> validates
+in the <i>DriverManager.getConnection</i> call, <ph conref="../conrefs.dita#prod/productshortname"></ph> validates
them against the properties defined for the current system.</p> <p>User names
are <i>SQL92Identifiers</i> and can be delimited.</p> </section>
<refsyn><title>Syntax</title> <codeblock><b>derby.user.{<b><i>UserName</i></b>=<b><i>Password</i></b>}<b><i> | UserName=userDN</i></b> }</b></codeblock
@@ -58,13 +58,13 @@
'<b><i>Password | userDN</i></b>')</b></codeblock> </refsyn>
<section><title>Default</title> <p>None.</p> </section>
<example><title>Example</title> <codeblock><b><ph>-- system-level property</ph>
-derby.user.guest=java5w</b></codeblock> <codeblock><b>derby.user.sa=<ph conref="tunconrefs.dita#prod/productshortname"></ph>3x9
+derby.user.guest=java5w</b></codeblock> <codeblock><b>derby.user.sa=<ph conref="../conrefs.dita#prod/productshortname"></ph>3x9
derby.user."!Amber"=java5w
<ph>-- database-level property</ph>
CALL SYSCS_UTIL.SYSCS_SET_DATABASE_PROPERTY(
'derby.user.sa',
- '<ph conref="tunconrefs.dita#prod/productshortname"></ph>3x9')
+ '<ph conref="../conrefs.dita#prod/productshortname"></ph>3x9')
<ph>-- cache a userDN locally, database-level property</ph>
CALL SYSCS_UTIL.SYSCS_SET_DATABASE_PROPERTY(
'derby.user.richard',
Modified: db/derby/docs/trunk/src/tuning/rtunproper27467.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/tuning/rtunproper27467.dita?view=diff&rev=524117&r1=524116&r2=524117
==============================================================================
--- db/derby/docs/trunk/src/tuning/rtunproper27467.dita (original)
+++ db/derby/docs/trunk/src/tuning/rtunproper27467.dita Fri Mar 30 08:14:48 2007
@@ -24,12 +24,12 @@
</metadata>
</prolog><refbody>
<section><title>Function</title>
-<p>Turns on user authentication for <ph conref="tunconrefs.dita#prod/productshortname"></ph>.</p>
+<p>Turns on user authentication for <ph conref="../conrefs.dita#prod/productshortname"></ph>.</p>
<p>When user authentication is turned on, a connection request must provide
a valid user name and password.</p>
-<p><ph conref="tunconrefs.dita#prod/productshortname"></ph> uses the type of user authentication specified with the <i><xref href="rtunproper13766.dita#rtunproper13766">derby.authentication.provider</xref></i> property.</p>
+<p><ph conref="../conrefs.dita#prod/productshortname"></ph> uses the type of user authentication specified with the <i><xref href="rtunproper13766.dita#rtunproper13766">derby.authentication.provider</xref></i> property.</p>
<p>For more information about user authentication, see "Working with User
-Authentication" in Chapter 7 of the <cite><ph conref="tunconrefs.dita#pub/citdevelop"></ph></cite>.</p>
+Authentication" in Chapter 7 of the <cite><ph conref="../conrefs.dita#pub/citdevelop"></ph></cite>.</p>
</section>
<section><title>Default</title>
<p>False.</p>
@@ -44,7 +44,7 @@
'true')</b></codeblock>
</example>
<section><title>Dynamic or static</title>
-<p>Static. For system-wide properties, you must reboot <ph conref="tunconrefs.dita#prod/productshortname"></ph> for the
+<p>Static. For system-wide properties, you must reboot <ph conref="../conrefs.dita#prod/productshortname"></ph> for the
change to take effect. For database-wide properties, you must reboot the database
for the change to take effect.</p>
</section></refbody></reference>
Modified: db/derby/docs/trunk/src/tuning/rtunproper27529.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/tuning/rtunproper27529.dita?view=diff&rev=524117&r1=524116&r2=524117
==============================================================================
--- db/derby/docs/trunk/src/tuning/rtunproper27529.dita (original)
+++ db/derby/docs/trunk/src/tuning/rtunproper27529.dita Fri Mar 30 08:14:48 2007
@@ -24,11 +24,11 @@
</metadata>
</prolog><refbody>
<section><title>Function</title>
-<p>The on-disk size of a <ph conref="tunconrefs.dita#prod/productshortname"></ph> table grows by one page at a time until
+<p>The on-disk size of a <ph conref="../conrefs.dita#prod/productshortname"></ph> table grows by one page at a time until
eight pages of user data (or nine pages of total disk use, one is used for
overhead) have been allocated. Then it will grow by eight pages at a time
if possible.</p>
-<p>A <ph conref="tunconrefs.dita#prod/productshortname"></ph> table or index can be created with a number of pages already
+<p>A <ph conref="../conrefs.dita#prod/productshortname"></ph> table or index can be created with a number of pages already
pre-allocated. To do so, specify the property prior to the CREATE TABLE or
CREATE INDEX statement.</p>
<p>Define the number of user pages the table or index is to be created with.
@@ -39,7 +39,7 @@
pages when the data are loaded.</p>
<p>The total desired size of the table or index should be
<codeblock><b>(1+derby.storage.initialPages) * derby.storage.pageSize bytes.</b></codeblock></p>
-<p>When you create a table or an index after setting this property, <ph conref="tunconrefs.dita#prod/productshortname"></ph>
+<p>When you create a table or an index after setting this property, <ph conref="../conrefs.dita#prod/productshortname"></ph>
attempts to preallocate the requested number of user pages. However, the operations
do not fail even if they are unable to preallocate the requested number of
pages, as long as they allocate at least one page.</p>
Modified: db/derby/docs/trunk/src/tuning/rtunproper28026.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/tuning/rtunproper28026.dita?view=diff&rev=524117&r1=524116&r2=524117
==============================================================================
--- db/derby/docs/trunk/src/tuning/rtunproper28026.dita (original)
+++ db/derby/docs/trunk/src/tuning/rtunproper28026.dita Fri Mar 30 08:14:48 2007
@@ -42,7 +42,7 @@
</section>
<section><title>Minimum value</title>
<p>The minimum value is 0% and the maximum is 100%. If you specify a value
-outside this range, <ph conref="tunconrefs.dita#prod/productshortname"></ph> uses the default value of 20%. </p>
+outside this range, <ph conref="../conrefs.dita#prod/productshortname"></ph> uses the default value of 20%. </p>
</section>
<example><title>Example</title>
<codeblock><b><ph>-- modifying the default for the system</ph>
@@ -54,7 +54,7 @@
</b></codeblock>
</example>
<section><title>Dynamic or static</title>
-<p>This property is dynamic; if you change it while <ph conref="tunconrefs.dita#prod/productshortname"></ph> is running,
+<p>This property is dynamic; if you change it while <ph conref="../conrefs.dita#prod/productshortname"></ph> is running,
the change takes effect immediately. For information about dynamic changes
to properties, see <xref href="ctunsetprop44147.dita#ctunsetprop44147"/>.</p>
</section></refbody></reference>
Modified: db/derby/docs/trunk/src/tuning/rtunproper32066.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/tuning/rtunproper32066.dita?view=diff&rev=524117&r1=524116&r2=524117
==============================================================================
--- db/derby/docs/trunk/src/tuning/rtunproper32066.dita (original)
+++ db/derby/docs/trunk/src/tuning/rtunproper32066.dita Fri Mar 30 08:14:48 2007
@@ -24,21 +24,21 @@
</metadata>
</prolog><refbody>
<section><title>Function</title>
-<p>Specifies the <ph conref="tunconrefs.dita#prod/productshortname"></ph> system directory, which is the directory that
+<p>Specifies the <ph conref="../conrefs.dita#prod/productshortname"></ph> system directory, which is the directory that
contains subdirectories holding databases that you create and the text file <i>derby.properties</i>.</p>
-<p>If the system directory that you specify with <i>derby.system.home</i> does not exist at startup, <ph conref="tunconrefs.dita#prod/productshortname"></ph> creates the directory automatically.</p>
+<p>If the system directory that you specify with <i>derby.system.home</i> does not exist at startup, <ph conref="../conrefs.dita#prod/productshortname"></ph> creates the directory automatically.</p>
</section>
<section><title>Default</title>
<p id="rtunproper11779">Current directory (the value of the JVM system property <i>user.dir</i>).</p>
-<p>If you do not explicitly set the <i>derby.system.home</i> property when starting <ph conref="tunconrefs.dita#prod/productshortname"></ph>, the default is the directory in
-which <ph conref="tunconrefs.dita#prod/productshortname"></ph> was started.
+<p>If you do not explicitly set the <i>derby.system.home</i> property when starting <ph conref="../conrefs.dita#prod/productshortname"></ph>, the default is the directory in
+which <ph conref="../conrefs.dita#prod/productshortname"></ph> was started.
<note>You should always explicitly
set the value of <i>derby.system.home</i>.</note></p>
</section>
<example><title>Example</title>
-<codeblock><b>-Dderby.system.home=C:\<ph conref="tunconrefs.dita#prod/productlowercase"></ph></b></codeblock>
+<codeblock><b>-Dderby.system.home=C:\<ph conref="../conrefs.dita#prod/productlowercase"></ph></b></codeblock>
</example>
<section><title>Dynamic or static</title>
-<p>This property is static; if you change it while <ph conref="tunconrefs.dita#prod/productshortname"></ph> is running,
+<p>This property is static; if you change it while <ph conref="../conrefs.dita#prod/productshortname"></ph> is running,
the change does not take effect until you reboot.</p>
</section></refbody></reference>
Modified: db/derby/docs/trunk/src/tuning/rtunproper33027.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/tuning/rtunproper33027.dita?view=diff&rev=524117&r1=524116&r2=524117
==============================================================================
--- db/derby/docs/trunk/src/tuning/rtunproper33027.dita (original)
+++ db/derby/docs/trunk/src/tuning/rtunproper33027.dita Fri Mar 30 08:14:48 2007
@@ -28,18 +28,18 @@
a stream to which the error log is written. The field is specified using the
fully qualified name of the class, then a dot (.) and then the field name.
The field must be public and static. Its type can be either <i>java.io.OutputStream</i> or <i>java.io.Writer</i>. </p> <p>The
-field is accessed once at <ph conref="tunconrefs.dita#prod/productshortname"></ph> boot
-time, and the value is used until <ph conref="tunconrefs.dita#prod/productshortname"></ph> is
+field is accessed once at <ph conref="../conrefs.dita#prod/productshortname"></ph> boot
+time, and the value is used until <ph conref="../conrefs.dita#prod/productshortname"></ph> is
rebooted. If the field is null, the error stream defaults to the system error
stream (<i>java.lang.System.err</i>).</p> <p>If the field does not exist or
is inaccessible, the error stream defaults to the system error stream. <ph
-conref="tunconrefs.dita#prod/productshortname"></ph> will not call the <i>close()</i> method
+conref="../conrefs.dita#prod/productshortname"></ph> will not call the <i>close()</i> method
of the object obtained from the field.</p> </section>
<section><title>Default</title> <p>None.</p> </section>
<example><title>Example</title> <codeblock><b>derby.stream.error.field=java.lang.System.err</b></codeblock> </example>
<section><title>Scope</title> <p><xref href="ctunproper51399.dita#ctunproper51399/rtunproper41229">system-wide</xref></p> </section>
<section><title>Dynamic or static</title> <p>This property is static; if you
-change it while <ph conref="tunconrefs.dita#prod/productshortname"></ph> is
+change it while <ph conref="../conrefs.dita#prod/productshortname"></ph> is
running, the change does not take effect until you reboot.</p> </section>
</refbody>
</reference>