Author: mcbrown
Date: 2009-11-02 08:58:50 +0100 (Mon, 02 Nov 2009)
New Revision: 17413
Log:
Fixing some auto-linking issues
Modified:
trunk/dynamic-docs/faq/mysql.xml
trunk/refman-5.1/dba-mysqld-server-core.xml
trunk/refman-5.1/functions-core.xml
trunk/refman-5.1/mysql-cluster-replication.xml
trunk/refman-5.1/optimization.xml
trunk/refman-5.1/sql-syntax-compound-statements.xml
trunk/refman-5.1/sql-syntax-transactions.xml
Modified: trunk/dynamic-docs/faq/mysql.xml
===================================================================
--- trunk/dynamic-docs/faq/mysql.xml 2009-11-02 01:04:09 UTC (rev 17412)
+++ trunk/dynamic-docs/faq/mysql.xml 2009-11-02 07:58:50 UTC (rev 17413)
Changed blocks: 3, Lines Added: 6, Lines Deleted: 6; 1320 bytes
@@ -1129,8 +1129,8 @@
<para>
Not in MySQL ¤t-series;. The SQL standard
- <literal role="stmt">SIGNAL</literal> and
- <literal role="stmt">RESIGNAL</literal> statements are
+ <literal>SIGNAL</literal> and
+ <literal>RESIGNAL</literal> statements are
implemented in MySQL 5.5.
</para>
@@ -1139,8 +1139,8 @@
<para>
Yes. As of MySQL 5.5, MySQL implements the SQL standard
- <literal role="stmt">SIGNAL</literal> and
- <literal role="stmt">RESIGNAL</literal> statements. See
+ <literal>SIGNAL</literal> and
+ <literal>RESIGNAL</literal> statements. See
<xref linkend="signal-resignal"/>.
</para>
@@ -1149,8 +1149,8 @@
<para>
Yes. As of MySQL 6.0.11, MySQL implements the SQL standard
- <literal role="stmt">SIGNAL</literal> and
- <literal role="stmt">RESIGNAL</literal> statements. See
+ <literal>SIGNAL</literal> and
+ <literal>RESIGNAL</literal> statements. See
<xref linkend="signal-resignal"/>.
</para>
Modified: trunk/refman-5.1/dba-mysqld-server-core.xml
===================================================================
--- trunk/refman-5.1/dba-mysqld-server-core.xml 2009-11-02 01:04:09 UTC (rev 17412)
+++ trunk/refman-5.1/dba-mysqld-server-core.xml 2009-11-02 07:58:50 UTC (rev 17413)
Changed blocks: 2, Lines Added: 6, Lines Deleted: 8; 1340 bytes
@@ -6006,10 +6006,9 @@
<para>
This value controls the demotion of buffers from the hot
- sublist of a key cache to the warm sublist. Lower values
- cause demotion to happen more quickly. The minimum value is
- 100. The default value is 300. See
- <xref linkend="myisam-key-cache"/>.
+ sublist of a key cache to the warm sublist. Lower values cause
+ demotion to happen more quickly. The minimum value is 100. The
+ default value is 300. See <xref linkend="myisam-key-cache"/>.
</para>
</listitem>
@@ -12217,11 +12216,10 @@
</para>
<para>
- (<literal>InnoDB Plugin</literal> only)
- Indicates whether the server was built with atomic
- instructions. This variable was added in in MySQL 5.1.38.
+ (<literal>InnoDB Plugin</literal> only) Indicates whether the
+ server was built with atomic instructions. This variable was
+ added in in MySQL 5.1.38.
</para>
-
</listitem>
<listitem>
Modified: trunk/refman-5.1/functions-core.xml
===================================================================
--- trunk/refman-5.1/functions-core.xml 2009-11-02 01:04:09 UTC (rev 17412)
+++ trunk/refman-5.1/functions-core.xml 2009-11-02 07:58:50 UTC (rev 17413)
Changed blocks: 2, Lines Added: 4, Lines Deleted: 5; 1582 bytes
@@ -7578,9 +7578,8 @@
<literal role="func">NOW()</literal> within a single query always
produce the same result. (For our purposes, a single query also
includes a call to a stored program (stored routine, trigger, or
- event) and all subprograms called by that program.) This
- principle also applies to
- <literal role="func">CURDATE()</literal>,
+ event) and all subprograms called by that program.) This principle
+ also applies to <literal role="func">CURDATE()</literal>,
<literal role="func">CURTIME()</literal>,
<literal role="func">UTC_DATE()</literal>,
<literal role="func">UTC_TIME()</literal>,
@@ -11710,8 +11709,8 @@
short or a stopword, but as a prefix that must be present in
the document in the form of a word that begins with the
prefix. Suppose that
- <literal role="sysvar">ft_min_word_len=4</literal>. Then a
- search for <literal>'+<replaceable>word</replaceable>
+ <literal role="sysvar" condition="ft_min_word_len">ft_min_word_len=4</literal>.
+ Then a search for <literal>'+<replaceable>word</replaceable>
+the*'</literal> will likely return fewer rows than a search
for <literal>'+<replaceable>word</replaceable>
+the'</literal>:
Modified: trunk/refman-5.1/mysql-cluster-replication.xml
===================================================================
--- trunk/refman-5.1/mysql-cluster-replication.xml 2009-11-02 01:04:09 UTC (rev 17412)
+++ trunk/refman-5.1/mysql-cluster-replication.xml 2009-11-02 07:58:50 UTC (rev 17413)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 723 bytes
@@ -2966,7 +2966,7 @@
<title>Logging full or partial rows (<option>--ndb-log-updated-only</option>
option)</title>
- <para id="option_mysqld_ndb_log_updated_only">
+ <para id="option_mysqld_ndb-log-updated-only">
For purposes of conflict resolution, there are two basic methods
of logging rows, as determined by the setting of the
<option>--ndb-log-updated-only</option> option for
Modified: trunk/refman-5.1/optimization.xml
===================================================================
--- trunk/refman-5.1/optimization.xml 2009-11-02 01:04:09 UTC (rev 17412)
+++ trunk/refman-5.1/optimization.xml 2009-11-02 07:58:50 UTC (rev 17413)
Changed blocks: 6, Lines Added: 20, Lines Deleted: 20; 4481 bytes
@@ -10179,12 +10179,13 @@
Usually the server follows an <firstterm>LRU (Least Recently
Used)</firstterm> strategy: When choosing a block for
replacement, it selects the least recently used index block. To
- make this choice easier, the key cache module maintains all used blocks in a
- special list (<firstterm>LRU chain</firstterm>) ordered by time of use.
- When a block is accessed, it is the most recently used and is placed at the end of the
- list. When blocks need to be replaced, blocks at the beginning
- of the list are the least recently used and become the first
- candidates for eviction.
+ make this choice easier, the key cache module maintains all used
+ blocks in a special list (<firstterm>LRU chain</firstterm>)
+ ordered by time of use. When a block is accessed, it is the most
+ recently used and is placed at the end of the list. When blocks
+ need to be replaced, blocks at the beginning of the list are the
+ least recently used and become the first candidates for
+ eviction.
</para>
<section id="shared-key-cache">
@@ -10403,9 +10404,8 @@
</itemizedlist>
<para>
-The
- <literal role="stmt">CACHE INDEX</literal> statement sets up an
- association between a table and a key cache, but the
+ The <literal role="stmt">CACHE INDEX</literal> statement sets
+ up an association between a table and a key cache, but the
association is lost each time the server restarts. If you want
the association to take effect each time the server starts,
one way to accomplish this is to use an option file: Include
@@ -10464,8 +10464,8 @@
<para>
When using the midpoint insertion strategy, the LRU chain is
- divided into two parts: a hot sublist and a warm sublist.
- The division point between two parts is not fixed, but the key
+ divided into two parts: a hot sublist and a warm sublist. The
+ division point between two parts is not fixed, but the key
cache management system takes care that the warm part is not
<quote>too short,</quote> always containing at least
<literal role="sysvar">key_cache_division_limit</literal>
@@ -10497,11 +10497,11 @@
</remark>
<para>
- A block promoted into the hot sublist is placed at the end
- of the list. The block then circulates within this sublist.
- If the block stays at the beginning of the sublist for a
- long enough time, it is demoted to the warm sublist. This time
- is determined by the value of the
+ A block promoted into the hot sublist is placed at the end of
+ the list. The block then circulates within this sublist. If
+ the block stays at the beginning of the sublist for a long
+ enough time, it is demoted to the warm sublist. This time is
+ determined by the value of the
<literal role="sysvar">key_cache_age_threshold</literal>
component of the key cache.
</para>
@@ -10509,8 +10509,8 @@
<para>
The threshold value prescribes that, for a key cache
containing <replaceable>N</replaceable> blocks, the block at
- the beginning of the hot sublist not accessed within the
- last <literal><replaceable>N</replaceable> ×
+ the beginning of the hot sublist not accessed within the last
+ <literal><replaceable>N</replaceable> ×
key_cache_age_threshold / 100</literal> hits is to be moved to
the beginning of the warm sublist. It then becomes the first
candidate for eviction, because blocks for replacement always
@@ -10533,8 +10533,8 @@
this, you must use a midpoint insertion strategy with the
<literal role="sysvar">key_cache_division_limit</literal> set
to much less than 100. Then valuable frequently hit nodes are
- preserved in the hot sublist during an index scan operation
- as well.
+ preserved in the hot sublist during an index scan operation as
+ well.
</para>
</section>
Modified: trunk/refman-5.1/sql-syntax-compound-statements.xml
===================================================================
--- trunk/refman-5.1/sql-syntax-compound-statements.xml 2009-11-02 01:04:09 UTC (rev 17412)
+++ trunk/refman-5.1/sql-syntax-compound-statements.xml 2009-11-02 07:58:50 UTC (rev 17413)
Changed blocks: 1, Lines Added: 2, Lines Deleted: 2; 617 bytes
@@ -145,8 +145,8 @@
</itemizedlist>
<para>
- The <literal role="stmt">SIGNAL</literal> and
- <literal role="stmt">RESIGNAL</literal> statements are not
+ The <literal>SIGNAL</literal> and
+ <literal>RESIGNAL</literal> statements are not
supported until MySQL 5.5.
</para>
Modified: trunk/refman-5.1/sql-syntax-transactions.xml
===================================================================
--- trunk/refman-5.1/sql-syntax-transactions.xml 2009-11-02 01:04:09 UTC (rev 17412)
+++ trunk/refman-5.1/sql-syntax-transactions.xml 2009-11-02 07:58:50 UTC (rev 17413)
Changed blocks: 1, Lines Added: 2, Lines Deleted: 2; 613 bytes
@@ -751,8 +751,8 @@
<para>
<literal role="stmt">LOCK TABLES</literal> and
- <literal role="stmt">UNLOCK TABLES</literal> cannot be used within
- stored programs.
+ <literal role="stmt" condition="lock-tables">UNLOCK
+ TABLES</literal> cannot be used within stored programs.
</para>
<para>
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r17413 - in trunk: dynamic-docs/faq refman-5.1 | martin.brown | 2 Nov |
