Author: paul
Date: 2009-02-25 21:07:13 +0100 (Wed, 25 Feb 2009)
New Revision: 13925
Log:
r38947@frost: paul | 2009-02-25 14:01:15 -0500
Add auto-link markup
Modified:
trunk/dynamic-docs/changelog/mysqld-1.xml
trunk/dynamic-docs/changelog/mysqld.xml
trunk/refman-4.1/data-types.xml
trunk/refman-4.1/dba-mysqld-server-core.xml
trunk/refman-4.1/errors-problems.xml
trunk/refman-4.1/extending-mysql.xml
trunk/refman-4.1/installing.xml
trunk/refman-4.1/news-4.0.xml
trunk/refman-4.1/optimization.xml
trunk/refman-4.1/sql-syntax-server-administration.xml
trunk/refman-5.0/data-types.xml
trunk/refman-5.0/dba-mysqld-server-core.xml
trunk/refman-5.0/errors-problems.xml
trunk/refman-5.0/extending-mysql.xml
trunk/refman-5.0/installing-core.xml
trunk/refman-5.0/installing-cs.xml
trunk/refman-5.0/optimization.xml
trunk/refman-5.0/sql-syntax-server-administration.xml
trunk/refman-5.1-maria/sql-syntax-server-administration.xml
trunk/refman-5.1/data-types.xml
trunk/refman-5.1/dba-mysqld-server-core.xml
trunk/refman-5.1/errors-problems-core.xml
trunk/refman-5.1/extending-mysql.xml
trunk/refman-5.1/installing-core.xml
trunk/refman-5.1/optimization.xml
trunk/refman-5.1/sql-syntax-server-administration.xml
trunk/refman-6.0/data-types.xml
trunk/refman-6.0/dba-mysqld-server-core.xml
trunk/refman-6.0/errors-problems.xml
trunk/refman-6.0/extending-mysql.xml
trunk/refman-6.0/installing-core.xml
trunk/refman-6.0/optimization.xml
trunk/refman-6.0/sql-syntax-server-administration.xml
trunk/refman-common/connector-odbc.xml
Property changes on: trunk
___________________________________________________________________
Name: svk:merge
- 4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:41755
7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:38945
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:36641
+ 4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:41755
7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:38947
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:36641
Modified: trunk/dynamic-docs/changelog/mysqld-1.xml
===================================================================
--- trunk/dynamic-docs/changelog/mysqld-1.xml 2009-02-25 19:39:56 UTC (rev 13924)
+++ trunk/dynamic-docs/changelog/mysqld-1.xml 2009-02-25 20:07:13 UTC (rev 13925)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 604 bytes
@@ -4032,7 +4032,7 @@
<para>
When using <command>mysql_install_db</command> on MySQL built
- with Sun Studio 12 with the <option>--with-debug</option> option
+ with Sun Studio 12 with the <option role="configure">--with-debug</option> option
enabled, the server would crash.
</para>
Modified: trunk/dynamic-docs/changelog/mysqld.xml
===================================================================
--- trunk/dynamic-docs/changelog/mysqld.xml 2009-02-25 19:39:56 UTC (rev 13924)
+++ trunk/dynamic-docs/changelog/mysqld.xml 2009-02-25 20:07:13 UTC (rev 13925)
Changed blocks: 2, Lines Added: 2, Lines Deleted: 2; 940 bytes
@@ -13547,7 +13547,7 @@
<message>
<para>
- A MySQL slave server built using <option>--with-debug</option>,
+ A MySQL slave server built using <option role="configure">--with-debug</option>,
and replicating itself, crashed.
</para>
@@ -84283,7 +84283,7 @@
<message>
<para>
- Using <option>--with-debug</option> to configure MySQL with
+ Using <option role="configure">--with-debug</option> to configure MySQL with
debugging support enables you to use the
<option>--debug="d,parser_debug"</option> option when you start
the server. This causes the Bison parser that is used to process
Modified: trunk/refman-4.1/data-types.xml
===================================================================
--- trunk/refman-4.1/data-types.xml 2009-02-25 19:39:56 UTC (rev 13924)
+++ trunk/refman-4.1/data-types.xml 2009-02-25 20:07:13 UTC (rev 13925)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 770 bytes
@@ -5164,7 +5164,7 @@
the column are used when sorting. The default value of
<literal role="sysvar">max_sort_length</literal> is 1024.
This value can be changed using the
- <option>--max_sort_length=<replaceable>N</replaceable></option>
+ <option role="sysvar">--max_sort_length=<replaceable>N</replaceable></option>
option when starting the <command>mysqld</command> server.
See <xref linkend="server-system-variables"/>.
</para>
Modified: trunk/refman-4.1/dba-mysqld-server-core.xml
===================================================================
--- trunk/refman-4.1/dba-mysqld-server-core.xml 2009-02-25 19:39:56 UTC (rev 13924)
+++ trunk/refman-4.1/dba-mysqld-server-core.xml 2009-02-25 20:07:13 UTC (rev 13925)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 675 bytes
@@ -617,7 +617,7 @@
</para>
<para>
- If MySQL is configured with <option>--with-debug</option>, you
+ If MySQL is configured with <option role="configure">--with-debug</option>, you
can use this option to get a trace file of what
<command>mysqld</command> is doing. The
<replaceable>debug_options</replaceable> string often is
Modified: trunk/refman-4.1/errors-problems.xml
===================================================================
--- trunk/refman-4.1/errors-problems.xml 2009-02-25 19:39:56 UTC (rev 13924)
+++ trunk/refman-4.1/errors-problems.xml 2009-02-25 20:07:13 UTC (rev 13925)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 871 bytes
@@ -3287,7 +3287,7 @@
wrong. Configuring MySQL for debugging causes a safe
memory allocator to be included that can find some errors.
It also provides a lot of output about what is happening.
- Reconfigure MySQL with the <option>--with-debug</option>
+ Reconfigure MySQL with the <option role="configure">--with-debug</option>
or <option>--with-debug=full</option> option to
<command>configure</command> and then recompile. See
<ulink url="http://forge.mysql.com/wiki/MySQL_Internals_Porting">MySQL
Modified: trunk/refman-4.1/extending-mysql.xml
===================================================================
--- trunk/refman-4.1/extending-mysql.xml 2009-02-25 19:39:56 UTC (rev 13924)
+++ trunk/refman-4.1/extending-mysql.xml 2009-02-25 20:07:13 UTC (rev 13925)
Changed blocks: 3, Lines Added: 4, Lines Deleted: 4; 1911 bytes
@@ -2424,7 +2424,7 @@
<para>
If you have some very specific problem, you can always try to
debug MySQL. To do this you must configure MySQL with the
- <option>--with-debug</option> or the
+ <option role="configure">--with-debug</option> or the
<option>--with-debug=full</option> option. You can check
whether MySQL was compiled with debugging by doing:
<command>mysqld --help</command>. If the
@@ -2466,11 +2466,11 @@
<para>
If <command>mysqld</command> stops crashing when you compile
- it with <option>--with-debug</option>, you probably have found
+ it with <option role="configure">--with-debug</option>, you probably have found
a compiler bug or a timing bug within MySQL. In this case, you
can try to add <option>-g</option> to the
<literal>CFLAGS</literal> and <literal>CXXFLAGS</literal>
- variables above and not use <option>--with-debug</option>. If
+ variables above and not use <option role="configure">--with-debug</option>. If
<command>mysqld</command> dies, you can at least attach to it
with <command>gdb</command> or use <command>gdb</command> on
the core file to find out what happened.
@@ -3147,7 +3147,7 @@
<para>
To be able to debug a MySQL client with the integrated debug
package, you should configure MySQL with
- <option>--with-debug</option> or
+ <option role="configure">--with-debug</option> or
<option>--with-debug=full</option>. See
<xref linkend="configure-options"/>.
</para>
Modified: trunk/refman-4.1/installing.xml
===================================================================
--- trunk/refman-4.1/installing.xml 2009-02-25 19:39:56 UTC (rev 13924)
+++ trunk/refman-4.1/installing.xml 2009-02-25 20:07:13 UTC (rev 13925)
Changed blocks: 4, Lines Added: 4, Lines Deleted: 4; 1679 bytes
@@ -1207,7 +1207,7 @@
<para>
If you want to compile a debug version of MySQL, you should
- add <option>--with-debug</option> or
+ add <option role="configure">--with-debug</option> or
<option>--with-debug=full</option> to the following
<command>configure</command> commands and remove any
<option>-fomit-frame-pointer</option> options.
@@ -8435,7 +8435,7 @@
</listitem>
<listitem>
- <para>
+ <para id="option_configure_with-debug">
<indexterm>
<primary>configure</primary>
<secondary>with-debug option</secondary>
@@ -8447,7 +8447,7 @@
</indexterm>
To configure MySQL with debugging code, use the
- <option>--with-debug</option> option:
+ <option role="configure">--with-debug</option> option:
</para>
<programlisting>
@@ -9398,7 +9398,7 @@
<para>
If you need to debug <command>mysqld</command> or a MySQL
client, run <command>configure</command> with the
- <option>--with-debug</option> option, and then recompile and
+ <option role="configure">--with-debug</option> option, and then recompile and
link your clients with the new client library. See
<ulink url="http://forge.mysql.com/wiki/MySQL_Internals_Porting">MySQL
Internals: Porting</ulink>.
Modified: trunk/refman-4.1/news-4.0.xml
===================================================================
--- trunk/refman-4.1/news-4.0.xml 2009-02-25 19:39:56 UTC (rev 13924)
+++ trunk/refman-4.1/news-4.0.xml 2009-02-25 20:07:13 UTC (rev 13925)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 576 bytes
@@ -2930,7 +2930,7 @@
<listitem>
<para>
Fixed a crash of the MySQL slave server when it was built with
- <option>--with-debug</option> and replicating itself. (Bug
+ <option role="configure">--with-debug</option> and replicating itself. (Bug
#3568)
</para>
</listitem>
Modified: trunk/refman-4.1/optimization.xml
===================================================================
--- trunk/refman-4.1/optimization.xml 2009-02-25 19:39:56 UTC (rev 13924)
+++ trunk/refman-4.1/optimization.xml 2009-02-25 20:07:13 UTC (rev 13925)
Changed blocks: 1, Lines Added: 2, Lines Deleted: 2; 1235 bytes
@@ -12794,14 +12794,14 @@
If you compile with <option>--with-debug=full</option>, most
queries are 20% slower. Some queries may take substantially
longer; for example, the MySQL benchmarks run 35% slower. If
- you use <option>--with-debug</option> (without
+ you use <option role="configure">--with-debug</option> (without
<literal>=full</literal>), the speed decrease is only 15%.
For a version of <command>mysqld</command> that has been
compiled with <option>--with-debug=full</option>, you can
disable memory checking at runtime by starting it with the
<option role="mysqld">--skip-safemalloc</option> option. The
execution speed should then be close to that obtained when
- configuring with <option>--with-debug</option>.
+ configuring with <option role="configure">--with-debug</option>.
</para>
</listitem>
Modified: trunk/refman-4.1/sql-syntax-server-administration.xml
===================================================================
--- trunk/refman-4.1/sql-syntax-server-administration.xml 2009-02-25 19:39:56 UTC (rev 13924)
+++ trunk/refman-4.1/sql-syntax-server-administration.xml 2009-02-25 20:07:13 UTC (rev 13925)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 743 bytes
@@ -7155,7 +7155,7 @@
the host tables enables further connection attempts from the
host. See <xref linkend="blocked-host"/>. You can start
<command>mysqld</command> with
- <option>--max_connect_errors=999999999</option> to avoid
+ <option role="sysvar">--max_connect_errors=999999999</option> to avoid
this error message.
</para>
</listitem>
Modified: trunk/refman-5.0/data-types.xml
===================================================================
--- trunk/refman-5.0/data-types.xml 2009-02-25 19:39:56 UTC (rev 13924)
+++ trunk/refman-5.0/data-types.xml 2009-02-25 20:07:13 UTC (rev 13925)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 770 bytes
@@ -4971,7 +4971,7 @@
the column are used when sorting. The default value of
<literal role="sysvar">max_sort_length</literal> is 1024.
This value can be changed using the
- <option>--max_sort_length=<replaceable>N</replaceable></option>
+ <option role="sysvar">--max_sort_length=<replaceable>N</replaceable></option>
option when starting the <command>mysqld</command> server.
See <xref linkend="server-system-variables"/>.
</para>
Modified: trunk/refman-5.0/dba-mysqld-server-core.xml
===================================================================
--- trunk/refman-5.0/dba-mysqld-server-core.xml 2009-02-25 19:39:56 UTC (rev 13924)
+++ trunk/refman-5.0/dba-mysqld-server-core.xml 2009-02-25 20:07:13 UTC (rev 13925)
Changed blocks: 2, Lines Added: 2, Lines Deleted: 2; 1150 bytes
@@ -709,7 +709,7 @@
<para condition="dynamic:optvar:item" role="5.0:mysqld:debug"/>
<para>
- If MySQL is configured with <option>--with-debug</option>, you
+ If MySQL is configured with <option role="configure">--with-debug</option>, you
can use this option to get a trace file of what
<command>mysqld</command> is doing. The
<replaceable>debug_options</replaceable> string often is
@@ -720,7 +720,7 @@
</para>
<para>
- As of MySQL 5.0.25, using <option>--with-debug</option> to
+ As of MySQL 5.0.25, using <option role="configure">--with-debug</option> to
configure MySQL with debugging support enables you to use the
<option>--debug="d,parser_debug"</option> option when you
start the server. This causes the Bison parser that is used to
Modified: trunk/refman-5.0/errors-problems.xml
===================================================================
--- trunk/refman-5.0/errors-problems.xml 2009-02-25 19:39:56 UTC (rev 13924)
+++ trunk/refman-5.0/errors-problems.xml 2009-02-25 20:07:13 UTC (rev 13925)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 871 bytes
@@ -3202,7 +3202,7 @@
wrong. Configuring MySQL for debugging causes a safe
memory allocator to be included that can find some errors.
It also provides a lot of output about what is happening.
- Reconfigure MySQL with the <option>--with-debug</option>
+ Reconfigure MySQL with the <option role="configure">--with-debug</option>
or <option>--with-debug=full</option> option to
<command>configure</command> and then recompile. See
<ulink url="http://forge.mysql.com/wiki/MySQL_Internals_Porting">MySQL
Modified: trunk/refman-5.0/extending-mysql.xml
===================================================================
--- trunk/refman-5.0/extending-mysql.xml 2009-02-25 19:39:56 UTC (rev 13924)
+++ trunk/refman-5.0/extending-mysql.xml 2009-02-25 20:07:13 UTC (rev 13925)
Changed blocks: 3, Lines Added: 4, Lines Deleted: 4; 1911 bytes
@@ -2538,7 +2538,7 @@
<para>
If you have some very specific problem, you can always try to
debug MySQL. To do this you must configure MySQL with the
- <option>--with-debug</option> or the
+ <option role="configure">--with-debug</option> or the
<option>--with-debug=full</option> option. You can check
whether MySQL was compiled with debugging by doing:
<command>mysqld --help</command>. If the
@@ -2580,11 +2580,11 @@
<para>
If <command>mysqld</command> stops crashing when you compile
- it with <option>--with-debug</option>, you probably have found
+ it with <option role="configure">--with-debug</option>, you probably have found
a compiler bug or a timing bug within MySQL. In this case, you
can try to add <option>-g</option> to the
<literal>CFLAGS</literal> and <literal>CXXFLAGS</literal>
- variables above and not use <option>--with-debug</option>. If
+ variables above and not use <option role="configure">--with-debug</option>. If
<command>mysqld</command> dies, you can at least attach to it
with <command>gdb</command> or use <command>gdb</command> on
the core file to find out what happened.
@@ -3345,7 +3345,7 @@
<para>
To be able to debug a MySQL client with the integrated debug
package, you should configure MySQL with
- <option>--with-debug</option> or
+ <option role="configure">--with-debug</option> or
<option>--with-debug=full</option>. See
<xref linkend="configure-options"/>.
</para>
Modified: trunk/refman-5.0/installing-core.xml
===================================================================
--- trunk/refman-5.0/installing-core.xml 2009-02-25 19:39:56 UTC (rev 13924)
+++ trunk/refman-5.0/installing-core.xml 2009-02-25 20:07:13 UTC (rev 13925)
Changed blocks: 4, Lines Added: 4, Lines Deleted: 4; 1721 bytes
@@ -7063,7 +7063,7 @@
</listitem>
<listitem>
- <para>
+ <para id="option_configure_with-debug">
<indexterm>
<primary>configure</primary>
<secondary>with-debug option</secondary>
@@ -7075,7 +7075,7 @@
</indexterm>
To configure MySQL with debugging code, use the
- <option>--with-debug</option> option:
+ <option role="configure">--with-debug</option> option:
</para>
<programlisting>
@@ -7091,7 +7091,7 @@
</para>
<para>
- As of MySQL 5.0.25, using <option>--with-debug</option> to
+ As of MySQL 5.0.25, using <option role="configure">--with-debug</option> to
configure MySQL with debugging support enables you to use
the <option>--debug="d,parser_debug"</option> option when
you start the server. This causes the Bison parser that is
@@ -8024,7 +8024,7 @@
<para>
If you need to debug <command>mysqld</command> or a MySQL
client, run <command>configure</command> with the
- <option>--with-debug</option> option, and then recompile and
+ <option role="configure">--with-debug</option> option, and then recompile and
link your clients with the new client library. See
<ulink url="http://forge.mysql.com/wiki/MySQL_Internals_Porting">MySQL
Internals: Porting</ulink>.
Modified: trunk/refman-5.0/installing-cs.xml
===================================================================
--- trunk/refman-5.0/installing-cs.xml 2009-02-25 19:39:56 UTC (rev 13924)
+++ trunk/refman-5.0/installing-cs.xml 2009-02-25 20:07:13 UTC (rev 13925)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 641 bytes
@@ -1202,7 +1202,7 @@
<para>
If you want to compile a debug version of MySQL, you should add
- <option>--with-debug</option> or
+ <option role="configure">--with-debug</option> or
<option>--with-debug=full</option> to the following
<command>configure</command> commands and remove any
<option>-fomit-frame-pointer</option> options.
Modified: trunk/refman-5.0/optimization.xml
===================================================================
--- trunk/refman-5.0/optimization.xml 2009-02-25 19:39:56 UTC (rev 13924)
+++ trunk/refman-5.0/optimization.xml 2009-02-25 20:07:13 UTC (rev 13925)
Changed blocks: 1, Lines Added: 2, Lines Deleted: 2; 1235 bytes
@@ -15358,14 +15358,14 @@
If you compile with <option>--with-debug=full</option>, most
queries are 20% slower. Some queries may take substantially
longer; for example, the MySQL benchmarks run 35% slower. If
- you use <option>--with-debug</option> (without
+ you use <option role="configure">--with-debug</option> (without
<literal>=full</literal>), the speed decrease is only 15%.
For a version of <command>mysqld</command> that has been
compiled with <option>--with-debug=full</option>, you can
disable memory checking at runtime by starting it with the
<option role="mysqld">--skip-safemalloc</option> option. The
execution speed should then be close to that obtained when
- configuring with <option>--with-debug</option>.
+ configuring with <option role="configure">--with-debug</option>.
</para>
</listitem>
Modified: trunk/refman-5.0/sql-syntax-server-administration.xml
===================================================================
--- trunk/refman-5.0/sql-syntax-server-administration.xml 2009-02-25 19:39:56 UTC (rev 13924)
+++ trunk/refman-5.0/sql-syntax-server-administration.xml 2009-02-25 20:07:13 UTC (rev 13925)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 743 bytes
@@ -8860,7 +8860,7 @@
the host tables enables further connection attempts from the
host. See <xref linkend="blocked-host"/>. You can start
<command>mysqld</command> with
- <option>--max_connect_errors=999999999</option> to avoid
+ <option role="sysvar">--max_connect_errors=999999999</option> to avoid
this error message.
</para>
</listitem>
Modified: trunk/refman-5.1/data-types.xml
===================================================================
--- trunk/refman-5.1/data-types.xml 2009-02-25 19:39:56 UTC (rev 13924)
+++ trunk/refman-5.1/data-types.xml 2009-02-25 20:07:13 UTC (rev 13925)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 770 bytes
@@ -4698,7 +4698,7 @@
the column are used when sorting. The default value of
<literal role="sysvar">max_sort_length</literal> is 1024.
This value can be changed using the
- <option>--max_sort_length=<replaceable>N</replaceable></option>
+ <option role="sysvar">--max_sort_length=<replaceable>N</replaceable></option>
option when starting the <command>mysqld</command> server.
See <xref linkend="server-system-variables"/>.
</para>
Modified: trunk/refman-5.1/dba-mysqld-server-core.xml
===================================================================
--- trunk/refman-5.1/dba-mysqld-server-core.xml 2009-02-25 19:39:56 UTC (rev 13924)
+++ trunk/refman-5.1/dba-mysqld-server-core.xml 2009-02-25 20:07:13 UTC (rev 13925)
Changed blocks: 2, Lines Added: 2, Lines Deleted: 2; 1150 bytes
@@ -750,7 +750,7 @@
<para condition="dynamic:optvar:item" role="5.1:mysqld:debug"/>
<para>
- If MySQL is configured with <option>--with-debug</option>, you
+ If MySQL is configured with <option role="configure">--with-debug</option>, you
can use this option to get a trace file of what
<command>mysqld</command> is doing. The
<replaceable>debug_options</replaceable> string often is
@@ -761,7 +761,7 @@
</para>
<para>
- As of MySQL 5.1.12, using <option>--with-debug</option> to
+ As of MySQL 5.1.12, using <option role="configure">--with-debug</option> to
configure MySQL with debugging support enables you to use the
<option>--debug="d,parser_debug"</option> option when you
start the server. This causes the Bison parser that is used to
Modified: trunk/refman-5.1/errors-problems-core.xml
===================================================================
--- trunk/refman-5.1/errors-problems-core.xml 2009-02-25 19:39:56 UTC (rev 13924)
+++ trunk/refman-5.1/errors-problems-core.xml 2009-02-25 20:07:13 UTC (rev 13925)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 886 bytes
@@ -3205,7 +3205,7 @@
wrong. Configuring MySQL for debugging causes a safe
memory allocator to be included that can find some errors.
It also provides a lot of output about what is happening.
- Reconfigure MySQL with the <option>--with-debug</option>
+ Reconfigure MySQL with the <option role="configure">--with-debug</option>
or <option>--with-debug=full</option> option to
<command>configure</command> and then recompile. See
<ulink url="http://forge.mysql.com/wiki/MySQL_Internals_Porting">MySQL
Modified: trunk/refman-5.1/extending-mysql.xml
===================================================================
--- trunk/refman-5.1/extending-mysql.xml 2009-02-25 19:39:56 UTC (rev 13924)
+++ trunk/refman-5.1/extending-mysql.xml 2009-02-25 20:07:13 UTC (rev 13925)
Changed blocks: 3, Lines Added: 4, Lines Deleted: 4; 1911 bytes
@@ -4629,7 +4629,7 @@
<para>
If you have some very specific problem, you can always try to
debug MySQL. To do this you must configure MySQL with the
- <option>--with-debug</option> or the
+ <option role="configure">--with-debug</option> or the
<option>--with-debug=full</option> option. You can check
whether MySQL was compiled with debugging by doing:
<command>mysqld --help</command>. If the
@@ -4671,11 +4671,11 @@
<para>
If <command>mysqld</command> stops crashing when you compile
- it with <option>--with-debug</option>, you probably have found
+ it with <option role="configure">--with-debug</option>, you probably have found
a compiler bug or a timing bug within MySQL. In this case, you
can try to add <option>-g</option> to the
<literal>CFLAGS</literal> and <literal>CXXFLAGS</literal>
- variables above and not use <option>--with-debug</option>. If
+ variables above and not use <option role="configure">--with-debug</option>. If
<command>mysqld</command> dies, you can at least attach to it
with <command>gdb</command> or use <command>gdb</command> on
the core file to find out what happened.
@@ -5457,7 +5457,7 @@
<para>
To be able to debug a MySQL client with the integrated debug
package, you should configure MySQL with
- <option>--with-debug</option> or
+ <option role="configure">--with-debug</option> or
<option>--with-debug=full</option>. See
<xref linkend="configure-options"/>.
</para>
Modified: trunk/refman-5.1/installing-core.xml
===================================================================
--- trunk/refman-5.1/installing-core.xml 2009-02-25 19:39:56 UTC (rev 13924)
+++ trunk/refman-5.1/installing-core.xml 2009-02-25 20:07:13 UTC (rev 13925)
Changed blocks: 5, Lines Added: 5, Lines Deleted: 5; 2121 bytes
@@ -1245,7 +1245,7 @@
<para>
If you want to compile a debug version of MySQL, you should
- add <option>--with-debug</option> or
+ add <option role="configure">--with-debug</option> or
<option>--with-debug=full</option> to the following
<command>configure</command> commands and remove any
<option>-fomit-frame-pointer</option> options.
@@ -8866,7 +8866,7 @@
</listitem>
<listitem>
- <para>
+ <para id="option_configure_with-debug">
<indexterm>
<primary>configure</primary>
<secondary>with-debug option</secondary>
@@ -8878,7 +8878,7 @@
</indexterm>
To configure MySQL with debugging code, use the
- <option>--with-debug</option> option:
+ <option role="configure">--with-debug</option> option:
</para>
<programlisting>
@@ -8894,7 +8894,7 @@
</para>
<para>
- As of MySQL 5.1.12, using <option>--with-debug</option> to
+ As of MySQL 5.1.12, using <option role="configure">--with-debug</option> to
configure MySQL with debugging support enables you to use
the <option>--debug="d,parser_debug"</option> option when
you start the server. This causes the Bison parser that is
@@ -9956,7 +9956,7 @@
<para>
If you need to debug <command>mysqld</command> or a MySQL
client, run <command>configure</command> with the
- <option>--with-debug</option> option, and then recompile and
+ <option role="configure">--with-debug</option> option, and then recompile and
link your clients with the new client library. See
<ulink url="http://forge.mysql.com/wiki/MySQL_Internals_Porting">MySQL
Internals: Porting</ulink>.
Modified: trunk/refman-5.1/optimization.xml
===================================================================
--- trunk/refman-5.1/optimization.xml 2009-02-25 19:39:56 UTC (rev 13924)
+++ trunk/refman-5.1/optimization.xml 2009-02-25 20:07:13 UTC (rev 13925)
Changed blocks: 1, Lines Added: 2, Lines Deleted: 2; 1235 bytes
@@ -16423,14 +16423,14 @@
If you compile with <option>--with-debug=full</option>, most
queries are 20% slower. Some queries may take substantially
longer; for example, the MySQL benchmarks run 35% slower. If
- you use <option>--with-debug</option> (without
+ you use <option role="configure">--with-debug</option> (without
<literal>=full</literal>), the speed decrease is only 15%.
For a version of <command>mysqld</command> that has been
compiled with <option>--with-debug=full</option>, you can
disable memory checking at runtime by starting it with the
<option role="mysqld">--skip-safemalloc</option> option. The
execution speed should then be close to that obtained when
- configuring with <option>--with-debug</option>.
+ configuring with <option role="configure">--with-debug</option>.
</para>
</listitem>
Modified: trunk/refman-5.1/sql-syntax-server-administration.xml
===================================================================
--- trunk/refman-5.1/sql-syntax-server-administration.xml 2009-02-25 19:39:56 UTC (rev 13924)
+++ trunk/refman-5.1/sql-syntax-server-administration.xml 2009-02-25 20:07:13 UTC (rev 13925)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 743 bytes
@@ -9957,7 +9957,7 @@
the host tables enables further connection attempts from the
host. See <xref linkend="blocked-host"/>. You can start
<command>mysqld</command> with
- <option>--max_connect_errors=999999999</option> to avoid
+ <option role="sysvar">--max_connect_errors=999999999</option> to avoid
this error message.
</para>
</listitem>
Modified: trunk/refman-5.1-maria/sql-syntax-server-administration.xml
===================================================================
--- trunk/refman-5.1-maria/sql-syntax-server-administration.xml 2009-02-25 19:39:56 UTC (rev 13924)
+++ trunk/refman-5.1-maria/sql-syntax-server-administration.xml 2009-02-25 20:07:13 UTC (rev 13925)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 763 bytes
@@ -10038,7 +10038,7 @@
the host tables enables further connection attempts from the
host. See <xref linkend="blocked-host"/>. You can start
<command>mysqld</command> with
- <option>--max_connect_errors=999999999</option> to avoid
+ <option role="sysvar">--max_connect_errors=999999999</option> to avoid
this error message.
</para>
</listitem>
Modified: trunk/refman-6.0/data-types.xml
===================================================================
--- trunk/refman-6.0/data-types.xml 2009-02-25 19:39:56 UTC (rev 13924)
+++ trunk/refman-6.0/data-types.xml 2009-02-25 20:07:13 UTC (rev 13925)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 770 bytes
@@ -4690,7 +4690,7 @@
the column are used when sorting. The default value of
<literal role="sysvar">max_sort_length</literal> is 1024.
This value can be changed using the
- <option>--max_sort_length=<replaceable>N</replaceable></option>
+ <option role="sysvar">--max_sort_length=<replaceable>N</replaceable></option>
option when starting the <command>mysqld</command> server.
See <xref linkend="server-system-variables"/>.
</para>
Modified: trunk/refman-6.0/dba-mysqld-server-core.xml
===================================================================
--- trunk/refman-6.0/dba-mysqld-server-core.xml 2009-02-25 19:39:56 UTC (rev 13924)
+++ trunk/refman-6.0/dba-mysqld-server-core.xml 2009-02-25 20:07:13 UTC (rev 13925)
Changed blocks: 2, Lines Added: 2, Lines Deleted: 2; 1131 bytes
@@ -730,7 +730,7 @@
<para condition="dynamic:optvar:item" role="6.0:mysqld:debug"/>
<para>
- If MySQL is configured with <option>--with-debug</option>, you
+ If MySQL is configured with <option role="configure">--with-debug</option>, you
can use this option to get a trace file of what
<command>mysqld</command> is doing. The
<replaceable>debug_options</replaceable> string often is
@@ -741,7 +741,7 @@
</para>
<para>
- Using <option>--with-debug</option> to configure MySQL with
+ Using <option role="configure">--with-debug</option> to configure MySQL with
debugging support enables you to use the
<option>--debug="d,parser_debug"</option> option when you
start the server. This causes the Bison parser that is used to
Modified: trunk/refman-6.0/errors-problems.xml
===================================================================
--- trunk/refman-6.0/errors-problems.xml 2009-02-25 19:39:56 UTC (rev 13924)
+++ trunk/refman-6.0/errors-problems.xml 2009-02-25 20:07:13 UTC (rev 13925)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 871 bytes
@@ -3192,7 +3192,7 @@
wrong. Configuring MySQL for debugging causes a safe
memory allocator to be included that can find some errors.
It also provides a lot of output about what is happening.
- Reconfigure MySQL with the <option>--with-debug</option>
+ Reconfigure MySQL with the <option role="configure">--with-debug</option>
or <option>--with-debug=full</option> option to
<command>configure</command> and then recompile. See
<ulink url="http://forge.mysql.com/wiki/MySQL_Internals_Porting">MySQL
Modified: trunk/refman-6.0/extending-mysql.xml
===================================================================
--- trunk/refman-6.0/extending-mysql.xml 2009-02-25 19:39:56 UTC (rev 13924)
+++ trunk/refman-6.0/extending-mysql.xml 2009-02-25 20:07:13 UTC (rev 13925)
Changed blocks: 3, Lines Added: 4, Lines Deleted: 4; 1911 bytes
@@ -4646,7 +4646,7 @@
<para>
If you have some very specific problem, you can always try to
debug MySQL. To do this you must configure MySQL with the
- <option>--with-debug</option> or the
+ <option role="configure">--with-debug</option> or the
<option>--with-debug=full</option> option. You can check
whether MySQL was compiled with debugging by doing:
<command>mysqld --help</command>. If the
@@ -4688,11 +4688,11 @@
<para>
If <command>mysqld</command> stops crashing when you compile
- it with <option>--with-debug</option>, you probably have found
+ it with <option role="configure">--with-debug</option>, you probably have found
a compiler bug or a timing bug within MySQL. In this case, you
can try to add <option>-g</option> to the
<literal>CFLAGS</literal> and <literal>CXXFLAGS</literal>
- variables above and not use <option>--with-debug</option>. If
+ variables above and not use <option role="configure">--with-debug</option>. If
<command>mysqld</command> dies, you can at least attach to it
with <command>gdb</command> or use <command>gdb</command> on
the core file to find out what happened.
@@ -5491,7 +5491,7 @@
<para>
To be able to debug a MySQL client with the integrated debug
package, you should configure MySQL with
- <option>--with-debug</option> or
+ <option role="configure">--with-debug</option> or
<option>--with-debug=full</option>. See
<xref linkend="configure-options"/>.
</para>
Modified: trunk/refman-6.0/installing-core.xml
===================================================================
--- trunk/refman-6.0/installing-core.xml 2009-02-25 19:39:56 UTC (rev 13924)
+++ trunk/refman-6.0/installing-core.xml 2009-02-25 20:07:13 UTC (rev 13925)
Changed blocks: 6, Lines Added: 6, Lines Deleted: 6; 2511 bytes
@@ -1245,7 +1245,7 @@
<para>
If you want to compile a debug version of MySQL, you should
- add <option>--with-debug</option> or
+ add <option role="configure">--with-debug</option> or
<option>--with-debug=full</option> to the following
<command>configure</command> commands and remove any
<option>-fomit-frame-pointer</option> options.
@@ -8457,7 +8457,7 @@
</listitem>
<listitem>
- <para>
+ <para id="option_configure_with-debug">
<indexterm>
<primary>configure</primary>
<secondary>with-debug option</secondary>
@@ -8469,7 +8469,7 @@
</indexterm>
To configure MySQL with debugging code, use the
- <option>--with-debug</option> option:
+ <option role="configure">--with-debug</option> option:
</para>
<programlisting>
@@ -8485,7 +8485,7 @@
</para>
<para>
- Using <option>--with-debug</option> to configure MySQL with
+ Using <option role="configure">--with-debug</option> to configure MySQL with
debugging support enables you to use the
<option>--debug="d,parser_debug"</option> option when you
start the server. This causes the Bison parser that is used
@@ -8521,7 +8521,7 @@
<para>
Debug Sync is also compiled in if you configure with the
- <option>--with-debug</option> option (which implies
+ <option role="configure">--with-debug</option> option (which implies
<option>--enable-debug-sync</option>), unless you also use
the <option>--disable-debug-sync</option> option.
</para>
@@ -9619,7 +9619,7 @@
<para>
If you need to debug <command>mysqld</command> or a MySQL
client, run <command>configure</command> with the
- <option>--with-debug</option> option, and then recompile and
+ <option role="configure">--with-debug</option> option, and then recompile and
link your clients with the new client library. See
<ulink url="http://forge.mysql.com/wiki/MySQL_Internals_Porting">MySQL
Internals: Porting</ulink>.
Modified: trunk/refman-6.0/optimization.xml
===================================================================
--- trunk/refman-6.0/optimization.xml 2009-02-25 19:39:56 UTC (rev 13924)
+++ trunk/refman-6.0/optimization.xml 2009-02-25 20:07:13 UTC (rev 13925)
Changed blocks: 1, Lines Added: 2, Lines Deleted: 2; 1235 bytes
@@ -16981,14 +16981,14 @@
If you compile with <option>--with-debug=full</option>, most
queries are 20% slower. Some queries may take substantially
longer; for example, the MySQL benchmarks run 35% slower. If
- you use <option>--with-debug</option> (without
+ you use <option role="configure">--with-debug</option> (without
<literal>=full</literal>), the speed decrease is only 15%.
For a version of <command>mysqld</command> that has been
compiled with <option>--with-debug=full</option>, you can
disable memory checking at runtime by starting it with the
<option role="mysqld">--skip-safemalloc</option> option. The
execution speed should then be close to that obtained when
- configuring with <option>--with-debug</option>.
+ configuring with <option role="configure">--with-debug</option>.
</para>
</listitem>
Modified: trunk/refman-6.0/sql-syntax-server-administration.xml
===================================================================
--- trunk/refman-6.0/sql-syntax-server-administration.xml 2009-02-25 19:39:56 UTC (rev 13924)
+++ trunk/refman-6.0/sql-syntax-server-administration.xml 2009-02-25 20:07:13 UTC (rev 13925)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 743 bytes
@@ -9844,7 +9844,7 @@
the host tables enables further connection attempts from the
host. See <xref linkend="blocked-host"/>. You can start
<command>mysqld</command> with
- <option>--max_connect_errors=999999999</option> to avoid
+ <option role="sysvar">--max_connect_errors=999999999</option> to avoid
this error message.
</para>
</listitem>
Modified: trunk/refman-common/connector-odbc.xml
===================================================================
--- trunk/refman-common/connector-odbc.xml 2009-02-25 19:39:56 UTC (rev 13924)
+++ trunk/refman-common/connector-odbc.xml 2009-02-25 20:07:13 UTC (rev 13925)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 657 bytes
@@ -2013,7 +2013,7 @@
<para>
To enable debugging information, build the driver from
source distribution and use the
- <option>--with-debug</option> option when you run
+ <option role="configure">--with-debug</option> option when you run
<command>configure</command>.
</para>
</listitem>
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r13925 - in trunk: . dynamic-docs/changelog refman-4.1 refman-5.0 refman-5.1 refman-5.1-maria refman-6.0 refman-common | paul.dubois | 25 Feb |
