Author: mcbrown
Date: 2007-04-25 12:19:36 +0200 (Wed, 25 Apr 2007)
New Revision: 6177
Log:
Updating manual for the Porting stuff which is now in the MySQL Forge
Removed:
trunk/refman-4.1/problems.xml
Modified:
trunk/refman-4.1/apis-c.xml
trunk/refman-4.1/dba-core.xml
trunk/refman-4.1/errors-problems.xml
trunk/refman-4.1/installing.xml
trunk/refman-4.1/introduction.xml
trunk/refman-4.1/language-structure.xml
trunk/refman-4.1/mysql-cluster.xml
trunk/refman-4.1/storage-engines.xml
trunk/refman-4.1/tutorial.xml
trunk/refman-5.0/apis-c.xml
trunk/refman-5.0/client-utility-programs.xml
trunk/refman-5.0/dba-core.xml
trunk/refman-5.0/errors-problems.xml
trunk/refman-5.0/faqs.xml
trunk/refman-5.0/installing-cs.xml
trunk/refman-5.0/introduction.xml
trunk/refman-5.0/language-structure.xml
trunk/refman-5.0/mysql-cluster.xml
trunk/refman-5.0/news-5.0.xml
trunk/refman-5.0/releasenotes-cs-5.0.xml
trunk/refman-5.0/se-myisam.xml
trunk/refman-5.0/triggers.xml
trunk/refman-5.0/tutorial.xml
trunk/refman-5.1/apis-c.xml
trunk/refman-5.1/client-utility-programs.xml
trunk/refman-5.1/dba-core.xml
trunk/refman-5.1/errors-problems.xml
trunk/refman-5.1/faqs.xml
trunk/refman-5.1/information-schema.xml
trunk/refman-5.1/installing.xml
trunk/refman-5.1/introduction.xml
trunk/refman-5.1/language-structure.xml
trunk/refman-5.1/mysql-cluster.xml
trunk/refman-5.1/partitioning.xml
trunk/refman-5.1/se-myisam.xml
trunk/refman-5.1/storage-engines.xml
trunk/refman-5.1/triggers.xml
trunk/refman-5.1/tutorial.xml
trunk/refman-common/bug-reports.xml
Modified: trunk/refman-4.1/apis-c.xml
===================================================================
--- trunk/refman-4.1/apis-c.xml 2007-04-25 09:14:46 UTC (rev 6176)
+++ trunk/refman-4.1/apis-c.xml 2007-04-25 10:19:36 UTC (rev 6177)
Changed blocks: 1, Lines Added: 2, Lines Deleted: 2; 667 bytes
@@ -2052,8 +2052,8 @@
<literal>mysql_debug()</literal> uses the Fred Fish debug
library. To use this function, you must compile the client
library to support debugging. See
- <xref linkend="debugging-server"/>, and
- <xref linkend="debugging-client"/>.
+ <ulink url="http://forge.mysql.com/wiki/MySQL_Internals_Porting">MySQL
+ Internals: Porting</ulink>.
</para>
<para>
Modified: trunk/refman-4.1/dba-core.xml
===================================================================
--- trunk/refman-4.1/dba-core.xml 2007-04-25 09:14:46 UTC (rev 6176)
+++ trunk/refman-4.1/dba-core.xml 2007-04-25 10:19:36 UTC (rev 6177)
Changed blocks: 6, Lines Added: 17, Lines Deleted: 7; 3093 bytes
@@ -973,7 +973,9 @@
<replaceable>debug_options</replaceable> string often is
<literal>'d:t:o,<replaceable>file_name</replaceable>'</literal>.
The default is <literal>'d:t:i:o,mysqld.trace'</literal>.
- See <xref linkend="making-trace-files"/>.
+ See
+ <ulink url="http://forge.mysql.com/wiki/MySQL_Internals_Porting">MySQL
+ Internals: Porting</ulink>.
</para>
</listitem>
@@ -1349,8 +1351,9 @@
(needed to stop <command>mysqld</command> with
<literal>^C</literal> to set breakpoints) and disable
stack tracing and core file handling. See
- <xref linkend="using-gdb-on-mysqld"/>. This option was
- added in MySQL 4.0.14.
+ <ulink url="http://forge.mysql.com/wiki/MySQL_Internals_Porting">MySQL
+ Internals: Porting</ulink>. This option was added in MySQL
+ 4.0.14.
</para>
</listitem>
@@ -2098,7 +2101,9 @@
<para>
Only use one thread (for debugging under Linux). This
option is available only if the server is built with
- debugging enabled. See <xref linkend="debugging-server"/>.
+ debugging enabled. See
+ <ulink url="http://forge.mysql.com/wiki/MySQL_Internals_Porting">MySQL
+ Internals: Porting</ulink>.
</para>
</listitem>
@@ -2874,7 +2879,9 @@
do not write stack traces. This option is useful when you
are running <command>mysqld</command> under a debugger. On
some systems, you also must use this option to get a core
- file. See <xref linkend="debugging-server"/>.
+ file. See
+ <ulink url="http://forge.mysql.com/wiki/MySQL_Internals_Porting">MySQL
+ Internals: Porting</ulink>.
</para>
</listitem>
@@ -17077,7 +17084,9 @@
(for example, <option>--debug=d,general,query</option>).
This prints host and user information about attempted
connections, as well as information about each command
- issued. See <xref linkend="making-trace-files"/>.
+ issued. See
+ <ulink url="http://forge.mysql.com/wiki/MySQL_Internals_Porting">MySQL
+ Internals: Porting</ulink>.
</para>
</listitem>
@@ -24055,7 +24064,8 @@
On some operating systems, the error log contains a stack trace
if <command>mysqld</command> dies. The trace can be used to
determine where <command>mysqld</command> died. See
- <xref linkend="using-stack-trace"/>.
+ <ulink url="http://forge.mysql.com/wiki/MySQL_Internals_Porting">MySQL
+ Internals: Porting</ulink>.
</para>
<para>
Modified: trunk/refman-4.1/errors-problems.xml
===================================================================
--- trunk/refman-4.1/errors-problems.xml 2007-04-25 09:14:46 UTC (rev 6176)
+++ trunk/refman-4.1/errors-problems.xml 2007-04-25 10:19:36 UTC (rev 6177)
Changed blocks: 6, Lines Added: 14, Lines Deleted: 8; 2972 bytes
@@ -1261,7 +1261,8 @@
the tables involved were checked with <literal>CHECK
TABLE</literal> before you ran the query, can you provide
a reproducible test case? See
- <xref linkend="reproducible-test-case"/>.
+ <ulink url="http://forge.mysql.com/wiki/MySQL_Internals_Porting">MySQL
+ Internals: Porting</ulink>.
</para>
</listitem>
@@ -2890,9 +2891,9 @@
On some systems, you can find in the error log a stack trace
of where <command>mysqld</command> died that you can resolve
with the <literal>resolve_stack_dump</literal> program. See
- <xref linkend="using-stack-trace"/>. Note that the variable
- values written in the error log may not always be 100%
- correct.
+ <ulink url="http://forge.mysql.com/wiki/MySQL_Internals_Porting">MySQL
+ Internals: Porting</ulink>. Note that the variable values
+ written in the error log may not always be 100% correct.
</para>
<para>
@@ -3008,7 +3009,9 @@
<listitem>
<para>
Try to make a test case that we can use to repeat the
- problem. See <xref linkend="reproducible-test-case"/>.
+ problem. See
+ <ulink url="http://forge.mysql.com/wiki/MySQL_Internals_Porting">MySQL
+ Internals: Porting</ulink>.
</para>
</listitem>
@@ -3045,7 +3048,8 @@
Reconfigure MySQL with the <option>--with-debug</option>
or <option>--with-debug=full</option> option to
<command>configure</command> and then recompile. See
- <xref linkend="debugging-server"/>.
+ <ulink url="http://forge.mysql.com/wiki/MySQL_Internals_Porting">MySQL
+ Internals: Porting</ulink>.
</para>
</listitem>
@@ -3106,7 +3110,8 @@
<para>
Start <command>mysqld</command> from
<command>gdb</command> (or another debugger). See
- <xref linkend="using-gdb-on-mysqld"/>.
+ <ulink url="http://forge.mysql.com/wiki/MySQL_Internals_Porting">MySQL
+ Internals: Porting</ulink>.
</para>
</listitem>
@@ -4881,7 +4886,8 @@
For information about platform-specific issues, see the
installation and porting instructions in
<xref linkend="operating-system-specific-notes"/>, and
- <xref linkend="porting"/>.
+ <ulink url="http://forge.mysql.com/wiki/MySQL_Internals_Porting">MySQL
+ Internals: Porting</ulink>.
</para>
<section id="errors-in-3-23">
Modified: trunk/refman-4.1/installing.xml
===================================================================
--- trunk/refman-4.1/installing.xml 2007-04-25 09:14:46 UTC (rev 6176)
+++ trunk/refman-4.1/installing.xml 2007-04-25 10:19:36 UTC (rev 6177)
Changed blocks: 5, Lines Added: 11, Lines Deleted: 5; 2320 bytes
@@ -4597,7 +4597,8 @@
options. In this case, <command>mysqld</command> writes a log
file <filename>C:\mysqld.trace</filename> that should contain
the reason why <command>mysqld</command> doesn't start. See
- <xref linkend="making-trace-files"/>.
+ <ulink url="http://forge.mysql.com/wiki/MySQL_Internals_Porting">MySQL
+ Internals: Porting</ulink>.
</para>
<para>
@@ -8263,7 +8264,9 @@
<para>
This causes a safe memory allocator to be included that can
find some errors and that provides output about what is
- happening. See <xref linkend="debugging-server"/>.
+ happening. See
+ <ulink url="http://forge.mysql.com/wiki/MySQL_Internals_Porting">MySQL
+ Internals: Porting</ulink>.
</para>
</listitem>
@@ -9219,7 +9222,8 @@
client, run <command>configure</command> with the
<option>--with-debug</option> option, and then recompile and
link your clients with the new client library. See
- <xref linkend="debugging-client"/>.
+ <ulink url="http://forge.mysql.com/wiki/MySQL_Internals_Porting">MySQL
+ Internals: Porting</ulink>.
</para>
</listitem>
@@ -11575,7 +11579,8 @@
If you cannot get <command>mysqld</command> to start, you can
try to make a trace file to find the problem by using the
<option>--debug</option> option. See
- <xref linkend="making-trace-files"/>.
+ <ulink url="http://forge.mysql.com/wiki/MySQL_Internals_Porting">MySQL
+ Internals: Porting</ulink>.
</para>
</section>
@@ -15754,7 +15759,8 @@
<para>
If this does not help, you should compile a debug version and
run it with a trace file or under <command>gdb</command>. See
- <xref linkend="using-gdb-on-mysqld"/>.
+ <ulink url="http://forge.mysql.com/wiki/MySQL_Internals_Porting">MySQL
+ Internals: Porting</ulink>.
</para>
</section>
Modified: trunk/refman-4.1/introduction.xml
===================================================================
--- trunk/refman-4.1/introduction.xml 2007-04-25 09:14:46 UTC (rev 6176)
+++ trunk/refman-4.1/introduction.xml 2007-04-25 10:19:36 UTC (rev 6177)
Changed blocks: 1, Lines Added: 2, Lines Deleted: 1; 578 bytes
@@ -104,7 +104,8 @@
<para>
For tips on porting the MySQL Database Software to new
architectures or operating systems, see
- <xref linkend="porting"/>.
+ <ulink url="http://forge.mysql.com/wiki/MySQL_Internals_Porting">MySQL
+ Internals: Porting</ulink>.
</para>
</listitem>
Modified: trunk/refman-4.1/language-structure.xml
===================================================================
--- trunk/refman-4.1/language-structure.xml 2007-04-25 09:14:46 UTC (rev 6176)
+++ trunk/refman-4.1/language-structure.xml 2007-04-25 10:19:36 UTC (rev 6177)
Changed blocks: 4, Lines Added: 8, Lines Deleted: 10; 1704 bytes
@@ -1026,10 +1026,10 @@
expression <literal>1e + 3</literal> or as the number
<literal>1e+3</literal>.
</para>
-
+
<para>
A user variable cannot be used directly in an SQL statement as an
- identifier or as part of an identifier. See
+ identifier or as part of an identifier. See
<xref linkend="user-variables"/>, for more information and an
example of a workaround.
</para>
@@ -1976,14 +1976,12 @@
If you refer to a variable that has not been initialized, it has a
value of <literal>NULL</literal> and a type of string.
</para>
-
-
-
+
<para>
A user variable cannot be used directly in an SQL statement as an
identifier or as part of an identifier, even if it is set off with
backticks. This is shown in the following example:
-
+
<programlisting>
mysql> <userinput>SELECT c1 FROM t;</userinput>
+----+
@@ -2020,11 +2018,11 @@
+------+
1 row in set (0.00 sec)
</programlisting>
-
+
In MySQL 4.1 and earlier, you must assemble a string for the query
in application code, as shown here using PHP 5:
-
- <programlisting>
+
+<programlisting>
<?php
$mysqli = new mysqli("localhost", "user", "pass", "test");
@@ -2047,7 +2045,7 @@
$mysqli->close();
?>
</programlisting>
-
+
Assembling an SQL statement in this fashion is sometimes known as
<quote>Dynamic SQL</quote>.
</para>
Modified: trunk/refman-4.1/mysql-cluster.xml
===================================================================
--- trunk/refman-4.1/mysql-cluster.xml 2007-04-25 09:14:46 UTC (rev 6176)
+++ trunk/refman-4.1/mysql-cluster.xml 2007-04-25 10:19:36 UTC (rev 6177)
Changed blocks: 5, Lines Added: 12, Lines Deleted: 10; 2692 bytes
@@ -6395,7 +6395,7 @@
to define at least <literal>NodeId1</literal>,
<literal>NodeId2</literal>, and the parameters to change.
</para>
-
+
<important>
<para>
Any <literal>[TCP]</literal> sections in the
@@ -8689,7 +8689,7 @@
changes in the cluster system tables.
</para>
</listitem>
-
+
<listitem>
<para>
Online upgrades from MySQL 5.1.17 and earlier to 5.1.18 and
@@ -8698,8 +8698,9 @@
<literal>mysql.ndb_apply_status</literal> table. However, it
should not be necessary to shut down the cluster entirely,
if you follow this modified rolling restart procedure:
-
+
<orderedlist>
+
<listitem>
<para>
Stop the management server, update the
@@ -8708,17 +8709,17 @@
step for each management server in turn.
</para>
</listitem>
-
+
<listitem>
<para>
For each data node in turn: Stop the data node,
replace the <literal>ndbd</literal> binary with the
new version, then restart the data node. It is not
necessary to use <literal>--initial</literal> when
- restarting any of the data nodes.
+ restarting any of the data nodes.
</para>
</listitem>
-
+
<listitem>
<para>
Stop <emphasis>all</emphasis> SQL nodes. Replace the
@@ -8732,15 +8733,16 @@
<literal>mysql.ndb_apply_status</literal> uses the
<literal>NDB</literal> storage engine and is thus
shared between all SQL nodes — there may be
- conflicts between MySQL servers using the old and
- new versions of the table.
+ conflicts between MySQL servers using the old and new
+ versions of the table.
</para>
</listitem>
+
</orderedlist>
-
+
You can find more information about the changes to
<literal>ndb_apply_status</literal> in the <citetitle>MySQL
- 5.1 Manual</citetitle>.
+ 5.1 Manual</citetitle>.
</para>
</listitem>
Modified: trunk/refman-4.1/storage-engines.xml
===================================================================
--- trunk/refman-4.1/storage-engines.xml 2007-04-25 09:14:46 UTC (rev 6176)
+++ trunk/refman-4.1/storage-engines.xml 2007-04-25 10:19:36 UTC (rev 6177)
Changed blocks: 1, Lines Added: 2, Lines Deleted: 1; 722 bytes
@@ -1458,7 +1458,8 @@
corruption may have occurred during normal operation. This is
a bug. You should try to create a reproducible test case that
demonstrates the problem. See <xref linkend="crashing"/>, and
- <xref linkend="reproducible-test-case"/>.
+ <ulink url="http://forge.mysql.com/wiki/MySQL_Internals_Porting">MySQL
+ Internals: Porting</ulink>.
</para>
<formalpara role="mnmas">
Modified: trunk/refman-4.1/tutorial.xml
===================================================================
--- trunk/refman-4.1/tutorial.xml 2007-04-25 09:14:46 UTC (rev 6176)
+++ trunk/refman-4.1/tutorial.xml 2007-04-25 10:19:36 UTC (rev 6177)
Changed blocks: 2, Lines Added: 6, Lines Deleted: 6; 1521 bytes
@@ -2842,13 +2842,13 @@
| pet |
+---------------------+
</programlisting>
-
+
<para>
The name of the column in the output produced by this statement is
always
<literal>Tables_in_<replaceable>db_name</replaceable></literal>,
where <replaceable>db_name</replaceable> is the name of the
- database. See <xref linkend="show-tables"/>, for more information.
+ database. See <xref linkend="show-tables"/>, for more information.
</para>
<para>
@@ -2880,19 +2880,19 @@
specifies the column's default value. <literal>Extra</literal>
displays special information about columns; for example, if a
column was created with the <literal>AUTO_INCREMENT</literal>
- option, this is shown here.
+ option, this is shown here.
</para>
-
+
<para>
<literal>DESC</literal> is a short form of
<literal>DESCRIBE</literal>. See <xref linkend="describe"/>, for
more information.
</para>
-
+
<para>
You can obtain the <literal>CREATE TABLE</literal> statement
necessary to create an existing table using the <literal>SHOW
- CREATE TABLE</literal> statement. See
+ CREATE TABLE</literal> statement. See
<xref linkend="show-create-table"/>.
</para>
Modified: trunk/refman-5.0/apis-c.xml
===================================================================
--- trunk/refman-5.0/apis-c.xml 2007-04-25 09:14:46 UTC (rev 6176)
+++ trunk/refman-5.0/apis-c.xml 2007-04-25 10:19:36 UTC (rev 6177)
Changed blocks: 1, Lines Added: 2, Lines Deleted: 2; 667 bytes
@@ -2045,8 +2045,8 @@
<literal>mysql_debug()</literal> uses the Fred Fish debug
library. To use this function, you must compile the client
library to support debugging. See
- <xref linkend="debugging-server"/>, and
- <xref linkend="debugging-client"/>.
+ <ulink url="http://forge.mysql.com/wiki/MySQL_Internals_Porting">MySQL
+ Internals: Porting</ulink>.
</para>
<para>
Modified: trunk/refman-5.0/client-utility-programs.xml
===================================================================
--- trunk/refman-5.0/client-utility-programs.xml 2007-04-25 09:14:46 UTC (rev 6176)
+++ trunk/refman-5.0/client-utility-programs.xml 2007-04-25 10:19:36 UTC (rev 6177)
Changed blocks: 5, Lines Added: 6, Lines Deleted: 8; 1949 bytes
@@ -1279,8 +1279,6 @@
</cmdsynopsis>
</refsynopsisdiv>
-
-
<refsection id="myisamchk-description">
<title>Description</title>
@@ -8479,7 +8477,7 @@
</listitem>
<listitem>
- <para id="option_mysqlbinlog_host">
+ <para id="option_mysqlbinlog_host">
<indexterm>
<primary>mysqlbinlog</primary>
<secondary>host option</secondary>
@@ -10925,8 +10923,8 @@
Use <replaceable>charset_name</replaceable> as the default
character set. See <xref linkend="character-sets"/>. If no
character set is specified, <command>mysqldump</command>
- uses <literal>utf8</literal>,
- and earlier versions use <literal>latin1</literal>.
+ uses <literal>utf8</literal>, and earlier versions use
+ <literal>latin1</literal>.
</para>
</listitem>
@@ -12527,8 +12525,8 @@
database directories are located.
<command>mysqlhotcopy</command> works only for backing up
<literal>MyISAM</literal> and <literal>ISAM</literal> tables,
- and <literal>ARCHIVE</literal>
- tables. It runs on Unix and NetWare.
+ and <literal>ARCHIVE</literal> tables. It runs on Unix and
+ NetWare.
</para>
<remark role="todo">
@@ -14179,7 +14177,7 @@
</listitem>
<listitem>
- <para id="option_mysqlshow_debug">
+ <para id="option_mysqlshow_debug">
<indexterm>
<primary>mysqlshow</primary>
<secondary>debug option</secondary>
Modified: trunk/refman-5.0/dba-core.xml
===================================================================
--- trunk/refman-5.0/dba-core.xml 2007-04-25 09:14:46 UTC (rev 6176)
+++ trunk/refman-5.0/dba-core.xml 2007-04-25 10:19:36 UTC (rev 6177)
Changed blocks: 6, Lines Added: 16, Lines Deleted: 6; 2985 bytes
@@ -1008,7 +1008,9 @@
<replaceable>debug_options</replaceable> string often is
<literal>'d:t:o,<replaceable>file_name</replaceable>'</literal>.
The default is <literal>'d:t:i:o,mysqld.trace'</literal>.
- See <xref linkend="making-trace-files"/>.
+ See
+ <ulink url="http://forge.mysql.com/wiki/MySQL_Internals_Porting">MySQL
+ Internals: Porting</ulink>.
</para>
<para>
@@ -1368,7 +1370,8 @@
(needed to stop <command>mysqld</command> with
<literal>^C</literal> to set breakpoints) and disable
stack tracing and core file handling. See
- <xref linkend="using-gdb-on-mysqld"/>.
+ <ulink url="http://forge.mysql.com/wiki/MySQL_Internals_Porting">MySQL
+ Internals: Porting</ulink>.
</para>
</listitem>
@@ -2163,7 +2166,9 @@
<para>
Only use one thread (for debugging under Linux). This
option is available only if the server is built with
- debugging enabled. See <xref linkend="debugging-server"/>.
+ debugging enabled. See
+ <ulink url="http://forge.mysql.com/wiki/MySQL_Internals_Porting">MySQL
+ Internals: Porting</ulink>.
</para>
</listitem>
@@ -2870,7 +2875,9 @@
Don't write stack traces. This option is useful when you
are running <command>mysqld</command> under a debugger. On
some systems, you also must use this option to get a core
- file. See <xref linkend="debugging-server"/>.
+ file. See
+ <ulink url="http://forge.mysql.com/wiki/MySQL_Internals_Porting">MySQL
+ Internals: Porting</ulink>.
</para>
</listitem>
@@ -20643,7 +20650,9 @@
(for example, <option>--debug=d,general,query</option>).
This prints host and user information about attempted
connections, as well as information about each command
- issued. See <xref linkend="making-trace-files"/>.
+ issued. See
+ <ulink url="http://forge.mysql.com/wiki/MySQL_Internals_Porting">MySQL
+ Internals: Porting</ulink>.
</para>
</listitem>
@@ -27573,7 +27582,8 @@
On some operating systems, the error log contains a stack trace
if <command>mysqld</command> dies. The trace can be used to
determine where <command>mysqld</command> died. See
- <xref linkend="using-stack-trace"/>.
+ <ulink url="http://forge.mysql.com/wiki/MySQL_Internals_Porting">MySQL
+ Internals: Porting</ulink>.
</para>
<para>
Modified: trunk/refman-5.0/errors-problems.xml
===================================================================
--- trunk/refman-5.0/errors-problems.xml 2007-04-25 09:14:46 UTC (rev 6176)
+++ trunk/refman-5.0/errors-problems.xml 2007-04-25 10:19:36 UTC (rev 6177)
Changed blocks: 6, Lines Added: 14, Lines Deleted: 8; 2967 bytes
@@ -1276,7 +1276,8 @@
the tables involved were checked with <literal>CHECK
TABLE</literal> before you ran the query, can you provide
a reproducible test case? See
- <xref linkend="reproducible-test-case"/>.
+ <ulink url="http://forge.mysql.com/wiki/MySQL_Internals_Porting">MySQL
+ Internals: Porting</ulink>.
</para>
</listitem>
@@ -2825,9 +2826,9 @@
On some systems, you can find in the error log a stack trace
of where <command>mysqld</command> died that you can resolve
with the <literal>resolve_stack_dump</literal> program. See
- <xref linkend="using-stack-trace"/>. Note that the variable
- values written in the error log may not always be 100%
- correct.
+ <ulink url="http://forge.mysql.com/wiki/MySQL_Internals_Porting">MySQL
+ Internals: Porting</ulink>. Note that the variable values
+ written in the error log may not always be 100% correct.
</para>
<para>
@@ -2943,7 +2944,9 @@
<listitem>
<para>
Try to make a test case that we can use to repeat the
- problem. See <xref linkend="reproducible-test-case"/>.
+ problem. See
+ <ulink url="http://forge.mysql.com/wiki/MySQL_Internals_Porting">MySQL
+ Internals: Porting</ulink>.
</para>
</listitem>
@@ -2980,7 +2983,8 @@
Reconfigure MySQL with the <option>--with-debug</option>
or <option>--with-debug=full</option> option to
<command>configure</command> and then recompile. See
- <xref linkend="debugging-server"/>.
+ <ulink url="http://forge.mysql.com/wiki/MySQL_Internals_Porting">MySQL
+ Internals: Porting</ulink>.
</para>
</listitem>
@@ -3041,7 +3045,8 @@
<para>
Start <command>mysqld</command> from
<command>gdb</command> (or another debugger). See
- <xref linkend="using-gdb-on-mysqld"/>.
+ <ulink url="http://forge.mysql.com/wiki/MySQL_Internals_Porting">MySQL
+ Internals: Porting</ulink>.
</para>
</listitem>
@@ -4822,7 +4827,8 @@
For information about platform-specific issues, see the
installation and porting instructions in
<xref linkend="operating-system-specific-notes"/>, and
- <xref linkend="porting"/>.
+ <ulink url="http://forge.mysql.com/wiki/MySQL_Internals_Porting">MySQL
+ Internals: Porting</ulink>.
</para>
<section id="open-bugs">
Modified: trunk/refman-5.0/faqs.xml
===================================================================
--- trunk/refman-5.0/faqs.xml 2007-04-25 09:14:46 UTC (rev 6176)
+++ trunk/refman-5.0/faqs.xml 2007-04-25 10:19:36 UTC (rev 6177)
Changed blocks: 2, Lines Added: 17, Lines Deleted: 11; 2187 bytes
@@ -72,9 +72,10 @@
<answer>
<para>
- Yes. For the syntax required to perform multiple-table updates,
- see <xref linkend="update"/>; for that required to perform
- multiple-table deletes, see <xref linkend="delete"/>.
+ Yes. For the syntax required to perform multiple-table
+ updates, see <xref linkend="update"/>; for that required to
+ perform multiple-table deletes, see
+ <xref linkend="delete"/>.
</para>
<para>
@@ -3698,41 +3699,46 @@
</answer>
</qandaentry>
-
+
<qandaentry>
-
+
<question>
+
<indexterm>
<primary>MySQL Cluster</primary>
<secondary>using in a virtual machine</secondary>
</indexterm>
-
+
<para>
Can I run MySQL Cluster nodes inside virtual machines (such
- as those created by VMWare, Parallels, or Xen)?
+ as those created by VMWare, Parallels, or Xen)?
</para>
+
</question>
-
+
<answer>
+
<para>
This is possible but not recommended for a production
environment.
</para>
-
+
<para>
We have found that running MySQL Cluster processes inside a
- virtual machine can give rise to issues with timing and disk
+ virtual machine can give rise to issues with timing and disk
subsystems that have a strong negative impact on the
operation of the cluster. The behavior of the cluster is
often unpredictable in these cases.
</para>
-
+
<para>
If the issue can be reproduced outside the virtual
environment, then we may be able to provide assistance.
Otherwise, we cannot support it at this time.
</para>
+
</answer>
+
</qandaentry>
<qandaentry>
Modified: trunk/refman-5.0/installing-cs.xml
===================================================================
--- trunk/refman-5.0/installing-cs.xml 2007-04-25 09:14:46 UTC (rev 6176)
+++ trunk/refman-5.0/installing-cs.xml 2007-04-25 10:19:36 UTC (rev 6177)
Changed blocks: 6, Lines Added: 13, Lines Deleted: 9; 2713 bytes
@@ -3691,7 +3691,8 @@
options. In this case, <command>mysqld</command> writes a log
file <filename>C:\mysqld.trace</filename> that should contain
the reason why <command>mysqld</command> doesn't start. See
- <xref linkend="making-trace-files"/>.
+ <ulink url="http://forge.mysql.com/wiki/MySQL_Internals_Porting">MySQL
+ Internals: Porting</ulink>.
</para>
<para>
@@ -6271,10 +6272,8 @@
<para>
To obtain a source distribution for MySQL,
- <xref linkend="getting-mysql"/>.
-If you want to build MySQL from source on Windows, see
- <xref linkend="windows-source-build"/>.
-
+ <xref linkend="getting-mysql"/>. If you want to build MySQL from
+ source on Windows, see <xref linkend="windows-source-build"/>.
</para>
<para>
@@ -7356,7 +7355,9 @@
<para>
This causes a safe memory allocator to be included that can
find some errors and that provides output about what is
- happening. See <xref linkend="debugging-server"/>.
+ happening. See
+ <ulink url="http://forge.mysql.com/wiki/MySQL_Internals_Porting">MySQL
+ Internals: Porting</ulink>.
</para>
<para>
@@ -8263,7 +8264,8 @@
client, run <command>configure</command> with the
<option>--with-debug</option> option, and then recompile and
link your clients with the new client library. See
- <xref linkend="debugging-client"/>.
+ <ulink url="http://forge.mysql.com/wiki/MySQL_Internals_Porting">MySQL
+ Internals: Porting</ulink>.
</para>
</listitem>
@@ -10930,7 +10932,8 @@
If you cannot get <command>mysqld</command> to start, you can
try to make a trace file to find the problem by using the
<option>--debug</option> option. See
- <xref linkend="making-trace-files"/>.
+ <ulink url="http://forge.mysql.com/wiki/MySQL_Internals_Porting">MySQL
+ Internals: Porting</ulink>.
</para>
</section>
@@ -14669,7 +14672,8 @@
<para>
If this doesn't help, you should compile a debug version and
run it with a trace file or under <command>gdb</command>. See
- <xref linkend="using-gdb-on-mysqld"/>.
+ <ulink url="http://forge.mysql.com/wiki/MySQL_Internals_Porting">MySQL
+ Internals: Porting</ulink>.
</para>
</section>
Modified: trunk/refman-5.0/introduction.xml
===================================================================
--- trunk/refman-5.0/introduction.xml 2007-04-25 09:14:46 UTC (rev 6176)
+++ trunk/refman-5.0/introduction.xml 2007-04-25 10:19:36 UTC (rev 6177)
Changed blocks: 1, Lines Added: 2, Lines Deleted: 1; 578 bytes
@@ -116,7 +116,8 @@
<para>
For tips on porting the MySQL Database Software to new
architectures or operating systems, see
- <xref linkend="porting"/>.
+ <ulink url="http://forge.mysql.com/wiki/MySQL_Internals_Porting">MySQL
+ Internals: Porting</ulink>.
</para>
</listitem>
Modified: trunk/refman-5.0/language-structure.xml
===================================================================
--- trunk/refman-5.0/language-structure.xml 2007-04-25 09:14:46 UTC (rev 6176)
+++ trunk/refman-5.0/language-structure.xml 2007-04-25 10:19:36 UTC (rev 6177)
Changed blocks: 5, Lines Added: 10, Lines Deleted: 10; 2357 bytes
@@ -1009,11 +1009,11 @@
expression <literal>1e + 3</literal> or as the number
<literal>1e+3</literal>.
</para>
-
+
<para>
A user variable cannot be used directly in an SQL statement as an
- identifier or as part of an identifier. See
- <xref linkend="user-variables"/>, for more information and
+ identifier or as part of an identifier. See
+ <xref linkend="user-variables"/>, for more information and
examples of workarounds.
</para>
@@ -2036,12 +2036,12 @@
variable to <literal>0</literal>, <literal>0.0</literal>, or
<literal>''</literal> to define its type before you use it.
</para>
-
+
<para>
A user variable cannot be used directly in an SQL statement as an
identifier or as part of an identifier, even if it is set off with
backticks. This is shown in the following example:
-
+
<programlisting>
mysql> <userinput>SELECT c1 FROM t;</userinput>
+----+
@@ -2078,10 +2078,10 @@
+------+
1 row in set (0.00 sec)
</programlisting>
-
+
One way to work around this problem is to assemble a string for
the query in application code, as shown here using PHP 5:
-
+
<programlisting>
<?php
$mysqli = new mysqli("localhost", "user", "pass", "test");
@@ -2105,13 +2105,13 @@
$mysqli->close();
?>
</programlisting>
-
+
(Assembling an SQL statement in this fashion is sometimes known as
<quote>Dynamic SQL</quote>.) It is also possible to perform such
operations using prepared statements, without the need to
concatenate strings of SQL in client code. This example
illustrates how this can be done:
-
+
<programlisting>
mysql> <userinput>SET @c = "c1";</userinput>
Query OK, 0 rows affected (0.00 sec)
@@ -2136,7 +2136,7 @@
mysql> <userinput>DEALLOCATE PREPARE stmt;</userinput>
Query OK, 0 rows affected (0.00 sec)
</programlisting>
-
+
You cannot use a placeholder for the name of a database, table, or
column in an SQL prepared statement. See <xref linkend="sqlps"/>,
for more information.
Modified: trunk/refman-5.0/mysql-cluster.xml
===================================================================
--- trunk/refman-5.0/mysql-cluster.xml 2007-04-25 09:14:46 UTC (rev 6176)
+++ trunk/refman-5.0/mysql-cluster.xml 2007-04-25 10:19:36 UTC (rev 6177)
Changed blocks: 5, Lines Added: 12, Lines Deleted: 10; 2691 bytes
@@ -6418,7 +6418,7 @@
to define at least <literal>NodeId1</literal>,
<literal>NodeId2</literal>, and the parameters to change.
</para>
-
+
<important>
<para>
Any <literal>[TCP]</literal> sections in the
@@ -8714,7 +8714,7 @@
changes in the cluster system tables.
</para>
</listitem>
-
+
<listitem>
<para>
Online upgrades from MySQL 5.1.17 and earlier to 5.1.18 and
@@ -8723,8 +8723,9 @@
<literal>mysql.ndb_apply_status</literal> table. However, it
should not be necessary to shut down the cluster entirely,
if you follow this modified rolling restart procedure:
-
+
<orderedlist>
+
<listitem>
<para>
Stop the management server, update the
@@ -8733,17 +8734,17 @@
step for each management server in turn.
</para>
</listitem>
-
+
<listitem>
<para>
For each data node in turn: Stop the data node,
replace the <literal>ndbd</literal> binary with the
new version, then restart the data node. It is not
necessary to use <literal>--initial</literal> when
- restarting any of the data nodes.
+ restarting any of the data nodes.
</para>
</listitem>
-
+
<listitem>
<para>
Stop <emphasis>all</emphasis> SQL nodes. Replace the
@@ -8757,15 +8758,16 @@
<literal>mysql.ndb_apply_status</literal> uses the
<literal>NDB</literal> storage engine and is thus
shared between all SQL nodes — there may be
- conflicts between MySQL servers using the old and
- new versions of the table.
+ conflicts between MySQL servers using the old and new
+ versions of the table.
</para>
</listitem>
+
</orderedlist>
-
+
You can find more information about the changes to
<literal>ndb_apply_status</literal> in the <citetitle>MySQL
- 5.1 Manual</citetitle>.
+ 5.1 Manual</citetitle>.
</para>
</listitem>
Modified: trunk/refman-5.0/news-5.0.xml
===================================================================
--- trunk/refman-5.0/news-5.0.xml 2007-04-25 09:14:46 UTC (rev 6176)
+++ trunk/refman-5.0/news-5.0.xml 2007-04-25 10:19:36 UTC (rev 6177)
Changed blocks: 1, Lines Added: 4, Lines Deleted: 3; 583 bytes
@@ -1744,9 +1744,10 @@
<literal>DATETIME</literal> value to <literal>'0000'</literal>
when inserting it into a table. (Bug #19370)
</para>
-<para>
-This patch was reverted in MySQL 5.0.42.
-</para>
+
+ <para>
+ This patch was reverted in MySQL 5.0.42.
+ </para>
</listitem>
<listitem>
Modified: trunk/refman-5.0/releasenotes-cs-5.0.xml
===================================================================
--- trunk/refman-5.0/releasenotes-cs-5.0.xml 2007-04-25 09:14:46 UTC (rev 6176)
+++ trunk/refman-5.0/releasenotes-cs-5.0.xml 2007-04-25 10:19:36 UTC (rev 6177)
Changed blocks: 1, Lines Added: 3, Lines Deleted: 3; 688 bytes
@@ -1270,9 +1270,9 @@
<listitem>
<para>
- A multiple-table <literal>DELETE QUICK</literal> could sometimes
- cause one of the affected tables to become corrupted. (Bug
- #25048)
+ A multiple-table <literal>DELETE QUICK</literal> could
+ sometimes cause one of the affected tables to become
+ corrupted. (Bug #25048)
</para>
</listitem>
Modified: trunk/refman-5.0/se-myisam.xml
===================================================================
--- trunk/refman-5.0/se-myisam.xml 2007-04-25 09:14:46 UTC (rev 6176)
+++ trunk/refman-5.0/se-myisam.xml 2007-04-25 10:19:36 UTC (rev 6177)
Changed blocks: 1, Lines Added: 2, Lines Deleted: 1; 668 bytes
@@ -1069,7 +1069,8 @@
occurred during normal operation. This is a bug. You should try
to create a reproducible test case that demonstrates the
problem. See <xref linkend="crashing"/>, and
- <xref linkend="reproducible-test-case"/>.
+ <ulink url="http://forge.mysql.com/wiki/MySQL_Internals_Porting">MySQL
+ Internals: Porting</ulink>.
</para>
<formalpara role="mnmas">
Modified: trunk/refman-5.0/triggers.xml
===================================================================
--- trunk/refman-5.0/triggers.xml 2007-04-25 09:14:46 UTC (rev 6176)
+++ trunk/refman-5.0/triggers.xml 2007-04-25 10:19:36 UTC (rev 6177)
Changed blocks: 1, Lines Added: 2, Lines Deleted: 2; 611 bytes
@@ -780,8 +780,8 @@
</para>
<remark role="todo">
- [js] Add an example demonstrating a multiple-table insert, since we
- now link to this section from a FAQ question concerning these.
+ [js] Add an example demonstrating a multiple-table insert, since
+ we now link to this section from a FAQ question concerning these.
</remark>
<para>
Modified: trunk/refman-5.0/tutorial.xml
===================================================================
--- trunk/refman-5.0/tutorial.xml 2007-04-25 09:14:46 UTC (rev 6176)
+++ trunk/refman-5.0/tutorial.xml 2007-04-25 10:19:36 UTC (rev 6177)
Changed blocks: 3, Lines Added: 8, Lines Deleted: 8; 1966 bytes
@@ -2828,13 +2828,13 @@
| pet |
+---------------------+
</programlisting>
-
+
<para>
The name of the column in the output produced by this statement is
always
<literal>Tables_in_<replaceable>db_name</replaceable></literal>,
where <replaceable>db_name</replaceable> is the name of the
- database. See <xref linkend="show-tables"/>, for more information.
+ database. See <xref linkend="show-tables"/>, for more information.
</para>
<para>
@@ -2856,7 +2856,7 @@
| death | date | YES | | NULL | |
+---------+-------------+------+-----+---------+-------+
</programlisting>
-
+
<para>
<literal>Field</literal> indicates the column name,
<literal>Type</literal> is the data type for the column,
@@ -2866,22 +2866,22 @@
specifies the column's default value. <literal>Extra</literal>
displays special information about columns; for example, if a
column was created with the <literal>AUTO_INCREMENT</literal>
- option, this is shown here.
+ option, this is shown here.
</para>
-
+
<para>
<literal>DESC</literal> is a short form of
<literal>DESCRIBE</literal>. See <xref linkend="describe"/>, for
more information.
</para>
-
+
<para>
You can obtain the <literal>CREATE TABLE</literal> statement
necessary to create an existing table using the <literal>SHOW
- CREATE TABLE</literal> statement. See
+ CREATE TABLE</literal> statement. See
<xref linkend="show-create-table"/>.
</para>
-
+
<para>
If you have indexes on a table, <literal>SHOW INDEX FROM
<replaceable>tbl_name</replaceable></literal> produces information
Modified: trunk/refman-5.1/apis-c.xml
===================================================================
--- trunk/refman-5.1/apis-c.xml 2007-04-25 09:14:46 UTC (rev 6176)
+++ trunk/refman-5.1/apis-c.xml 2007-04-25 10:19:36 UTC (rev 6177)
Changed blocks: 1, Lines Added: 2, Lines Deleted: 2; 667 bytes
@@ -2035,8 +2035,8 @@
<literal>mysql_debug()</literal> uses the Fred Fish debug
library. To use this function, you must compile the client
library to support debugging. See
- <xref linkend="debugging-server"/>, and
- <xref linkend="debugging-client"/>.
+ <ulink url="http://forge.mysql.com/wiki/MySQL_Internals_Porting">MySQL
+ Internals: Porting</ulink>.
</para>
<para>
Modified: trunk/refman-5.1/client-utility-programs.xml
===================================================================
--- trunk/refman-5.1/client-utility-programs.xml 2007-04-25 09:14:46 UTC (rev 6176)
+++ trunk/refman-5.1/client-utility-programs.xml 2007-04-25 10:19:36 UTC (rev 6177)
Changed blocks: 4, Lines Added: 6, Lines Deleted: 7; 2102 bytes
@@ -8762,7 +8762,7 @@
</listitem>
<listitem>
- <para id="option_mysqlbinlog_set-charset">
+ <para id="option_mysqlbinlog_set-charset">
<indexterm>
<primary>mysqlbinlog</primary>
<secondary>set-charset option</secondary>
@@ -11077,8 +11077,8 @@
Use <replaceable>charset_name</replaceable> as the default
character set. See <xref linkend="character-sets"/>. If no
character set is specified, <command>mysqldump</command>
- uses <literal>utf8</literal>,
- and earlier versions use <literal>latin1</literal>.
+ uses <literal>utf8</literal>, and earlier versions use
+ <literal>latin1</literal>.
</para>
</listitem>
@@ -11526,8 +11526,7 @@
Lock all tables before dumping them. The tables are locked
with <literal>READ LOCAL</literal> to allow concurrent
inserts in the case of <literal>MyISAM</literal> tables.
- For transactional tables such as
- <literal>InnoDB</literal>
+ For transactional tables such as <literal>InnoDB</literal>
and <literal>BDB</literal>,
<option>--single-transaction</option> is a much better
option, because it does not need to lock the tables at
@@ -12730,8 +12729,8 @@
database directories are located.
<command>mysqlhotcopy</command> works only for backing up
<literal>MyISAM</literal> and <literal>ISAM</literal> tables,
- and <literal>ARCHIVE</literal>
- tables. It runs on Unix and NetWare.
+ and <literal>ARCHIVE</literal> tables. It runs on Unix and
+ NetWare.
</para>
<remark role="todo">
Modified: trunk/refman-5.1/dba-core.xml
===================================================================
--- trunk/refman-5.1/dba-core.xml 2007-04-25 09:14:46 UTC (rev 6176)
+++ trunk/refman-5.1/dba-core.xml 2007-04-25 10:19:36 UTC (rev 6177)
Changed blocks: 6, Lines Added: 16, Lines Deleted: 6; 2985 bytes
@@ -1036,7 +1036,9 @@
<replaceable>debug_options</replaceable> string often is
<literal>'d:t:o,<replaceable>file_name</replaceable>'</literal>.
The default is <literal>'d:t:i:o,mysqld.trace'</literal>.
- See <xref linkend="making-trace-files"/>.
+ See
+ <ulink url="http://forge.mysql.com/wiki/MySQL_Internals_Porting">MySQL
+ Internals: Porting</ulink>.
</para>
<para>
@@ -1454,7 +1456,8 @@
(needed to stop <command>mysqld</command> with
<literal>^C</literal> to set breakpoints) and disable
stack tracing and core file handling. See
- <xref linkend="using-gdb-on-mysqld"/>.
+ <ulink url="http://forge.mysql.com/wiki/MySQL_Internals_Porting">MySQL
+ Internals: Porting</ulink>.
</para>
</listitem>
@@ -2254,7 +2257,9 @@
<para>
Only use one thread (for debugging under Linux). This
option is available only if the server is built with
- debugging enabled. See <xref linkend="debugging-server"/>.
+ debugging enabled. See
+ <ulink url="http://forge.mysql.com/wiki/MySQL_Internals_Porting">MySQL
+ Internals: Porting</ulink>.
</para>
</listitem>
@@ -2909,7 +2914,9 @@
Don't write stack traces. This option is useful when you
are running <command>mysqld</command> under a debugger. On
some systems, you also must use this option to get a core
- file. See <xref linkend="debugging-server"/>.
+ file. See
+ <ulink url="http://forge.mysql.com/wiki/MySQL_Internals_Porting">MySQL
+ Internals: Porting</ulink>.
</para>
</listitem>
@@ -21321,7 +21328,9 @@
(for example, <option>--debug=d,general,query</option>).
This prints host and user information about attempted
connections, as well as information about each command
- issued. See <xref linkend="making-trace-files"/>.
+ issued. See
+ <ulink url="http://forge.mysql.com/wiki/MySQL_Internals_Porting">MySQL
+ Internals: Porting</ulink>.
</para>
</listitem>
@@ -28503,7 +28512,8 @@
On some operating systems, the error log contains a stack trace
if <command>mysqld</command> dies. The trace can be used to
determine where <command>mysqld</command> died. See
- <xref linkend="using-stack-trace"/>.
+ <ulink url="http://forge.mysql.com/wiki/MySQL_Internals_Porting">MySQL
+ Internals: Porting</ulink>.
</para>
<para>
Modified: trunk/refman-5.1/errors-problems.xml
===================================================================
--- trunk/refman-5.1/errors-problems.xml 2007-04-25 09:14:46 UTC (rev 6176)
+++ trunk/refman-5.1/errors-problems.xml 2007-04-25 10:19:36 UTC (rev 6177)
Changed blocks: 6, Lines Added: 14, Lines Deleted: 8; 2967 bytes
@@ -1278,7 +1278,8 @@
the tables involved were checked with <literal>CHECK
TABLE</literal> before you ran the query, can you provide
a reproducible test case? See
- <xref linkend="reproducible-test-case"/>.
+ <ulink url="http://forge.mysql.com/wiki/MySQL_Internals_Porting">MySQL
+ Internals: Porting</ulink>.
</para>
</listitem>
@@ -2826,9 +2827,9 @@
On some systems, you can find in the error log a stack trace
of where <command>mysqld</command> died that you can resolve
with the <literal>resolve_stack_dump</literal> program. See
- <xref linkend="using-stack-trace"/>. Note that the variable
- values written in the error log may not always be 100%
- correct.
+ <ulink url="http://forge.mysql.com/wiki/MySQL_Internals_Porting">MySQL
+ Internals: Porting</ulink>. Note that the variable values
+ written in the error log may not always be 100% correct.
</para>
<para>
@@ -2944,7 +2945,9 @@
<listitem>
<para>
Try to make a test case that we can use to repeat the
- problem. See <xref linkend="reproducible-test-case"/>.
+ problem. See
+ <ulink url="http://forge.mysql.com/wiki/MySQL_Internals_Porting">MySQL
+ Internals: Porting</ulink>.
</para>
</listitem>
@@ -2981,7 +2984,8 @@
Reconfigure MySQL with the <option>--with-debug</option>
or <option>--with-debug=full</option> option to
<command>configure</command> and then recompile. See
- <xref linkend="debugging-server"/>.
+ <ulink url="http://forge.mysql.com/wiki/MySQL_Internals_Porting">MySQL
+ Internals: Porting</ulink>.
</para>
</listitem>
@@ -3042,7 +3046,8 @@
<para>
Start <command>mysqld</command> from
<command>gdb</command> (or another debugger). See
- <xref linkend="using-gdb-on-mysqld"/>.
+ <ulink url="http://forge.mysql.com/wiki/MySQL_Internals_Porting">MySQL
+ Internals: Porting</ulink>.
</para>
</listitem>
@@ -4725,7 +4730,8 @@
For information about platform-specific issues, see the
installation and porting instructions in
<xref linkend="operating-system-specific-notes"/>, and
- <xref linkend="porting"/>.
+ <ulink url="http://forge.mysql.com/wiki/MySQL_Internals_Porting">MySQL
+ Internals: Porting</ulink>.
</para>
<section id="open-bugs">
Modified: trunk/refman-5.1/faqs.xml
===================================================================
--- trunk/refman-5.1/faqs.xml 2007-04-25 09:14:46 UTC (rev 6176)
+++ trunk/refman-5.1/faqs.xml 2007-04-25 10:19:36 UTC (rev 6177)
Changed blocks: 2, Lines Added: 19, Lines Deleted: 13; 2240 bytes
@@ -72,9 +72,10 @@
<answer>
<para>
- Yes. For the syntax required to perform multiple-table updates,
- see <xref linkend="update"/>; for that required to perform
- multiple-table deletes, see <xref linkend="delete"/>.
+ Yes. For the syntax required to perform multiple-table
+ updates, see <xref linkend="update"/>; for that required to
+ perform multiple-table deletes, see
+ <xref linkend="delete"/>.
</para>
<para>
@@ -3742,43 +3743,48 @@
</answer>
</qandaentry>
-
+
<qandaentry>
-
+
<question>
+
<indexterm>
<primary>MySQL Cluster</primary>
<secondary>using in a virtual machine</secondary>
</indexterm>
-
+
<para>
Can I run MySQL Cluster nodes inside virtual machines (such
- as those created by VMWare, Parallels, or Xen)?
+ as those created by VMWare, Parallels, or Xen)?
</para>
+
</question>
-
+
<answer>
+
<para>
This is possible but not recommended for a production
environment.
</para>
-
+
<para>
We have found that running MySQL Cluster processes inside a
- virtual machine can give rise to issues with timing and disk
+ virtual machine can give rise to issues with timing and disk
subsystems that have a strong negative impact on the
operation of the cluster. The behavior of the cluster is
often unpredictable in these cases.
</para>
-
+
<para>
If the issue can be reproduced outside the virtual
environment, then we may be able to provide assistance.
Otherwise, we cannot support it at this time.
</para>
+
</answer>
- </qandaentry>
-
+
+ </qandaentry>
+
<qandaentry>
<question>
Modified: trunk/refman-5.1/information-schema.xml
===================================================================
--- trunk/refman-5.1/information-schema.xml 2007-04-25 09:14:46 UTC (rev 6176)
+++ trunk/refman-5.1/information-schema.xml 2007-04-25 10:19:36 UTC (rev 6177)
Changed blocks: 4, Lines Added: 7, Lines Deleted: 9; 2201 bytes
@@ -4136,7 +4136,7 @@
</para>
<para>
- This column was added in MySQL 5.1.17. See
+ This column was added in MySQL 5.1.17. See
<xref linkend="news-5-1-17"/>, for important information if
you are using the Event Scheduler and are upgrading from MySQL
5.1.16 (or earlier) to MySQL 5.1.17 (or later).
@@ -4189,9 +4189,9 @@
addition or subtraction of any <literal>INTERVAL</literal>
value included in the event's <literal>AT</literal> clause.
For example, if an event is created using <literal>ON SCHEDULE
- AT CURRENT_TIMESTAMP + '1:6' DAY_HOUR</literal>, and the
- event was created at 2006-02-09 14:05:30, the value shown in
- this column would be <literal>'2006-02-10 20:05:30'</literal>.
+ AT CURRENT_TIMESTAMP + '1:6' DAY_HOUR</literal>, and the event
+ was created at 2006-02-09 14:05:30, the value shown in this
+ column would be <literal>'2006-02-10 20:05:30'</literal>.
</para>
<para>
@@ -4399,7 +4399,6 @@
1 row in set (0.50 sec)
</programlisting>
-
<para>
Prior to MySQL 5.1.17, the times displayed in the
<literal>STARTS</literal>, <literal>ENDS</literal>, and
@@ -4412,12 +4411,11 @@
<literal>last_executed</literal> columns of the
<literal>mysql.event</literal> table as well as the
<literal>Starts</literal> and <literal>Ends</literal> columns in
- the output of <literal>SHOW [FULL] EVENTS</literal>.)
+ the output of <literal>SHOW [FULL] EVENTS</literal>.)
</para>
-
+
<para>
- The
- <literal>CREATED</literal> and <literal>LAST_ALTERED</literal>
+ The <literal>CREATED</literal> and <literal>LAST_ALTERED</literal>
columns use the server time zone (as do the
<literal>created</literal> and <literal>last_altered</literal>
columns of the <literal>mysql.event</literal> table).
Modified: trunk/refman-5.1/installing.xml
===================================================================
--- trunk/refman-5.1/installing.xml 2007-04-25 09:14:46 UTC (rev 6176)
+++ trunk/refman-5.1/installing.xml 2007-04-25 10:19:36 UTC (rev 6177)
Changed blocks: 5, Lines Added: 11, Lines Deleted: 5; 2316 bytes
@@ -4495,7 +4495,8 @@
options. In this case, <command>mysqld</command> writes a log
file <filename>C:\mysqld.trace</filename> that should contain
the reason why <command>mysqld</command> doesn't start. See
- <xref linkend="making-trace-files"/>.
+ <ulink url="http://forge.mysql.com/wiki/MySQL_Internals_Porting">MySQL
+ Internals: Porting</ulink>.
</para>
<para>
@@ -8129,7 +8130,9 @@
<para>
This causes a safe memory allocator to be included that can
find some errors and that provides output about what is
- happening. See <xref linkend="debugging-server"/>.
+ happening. See
+ <ulink url="http://forge.mysql.com/wiki/MySQL_Internals_Porting">MySQL
+ Internals: Porting</ulink>.
</para>
<para>
@@ -9144,7 +9147,8 @@
client, run <command>configure</command> with the
<option>--with-debug</option> option, and then recompile and
link your clients with the new client library. See
- <xref linkend="debugging-client"/>.
+ <ulink url="http://forge.mysql.com/wiki/MySQL_Internals_Porting">MySQL
+ Internals: Porting</ulink>.
</para>
</listitem>
@@ -11503,7 +11507,8 @@
If you cannot get <command>mysqld</command> to start, you can
try to make a trace file to find the problem by using the
<option>--debug</option> option. See
- <xref linkend="making-trace-files"/>.
+ <ulink url="http://forge.mysql.com/wiki/MySQL_Internals_Porting">MySQL
+ Internals: Porting</ulink>.
</para>
</section>
@@ -14625,7 +14630,8 @@
<para>
If this doesn't help, you should compile a debug version and
run it with a trace file or under <command>gdb</command>. See
- <xref linkend="using-gdb-on-mysqld"/>.
+ <ulink url="http://forge.mysql.com/wiki/MySQL_Internals_Porting">MySQL
+ Internals: Porting</ulink>.
</para>
</section>
Modified: trunk/refman-5.1/introduction.xml
===================================================================
--- trunk/refman-5.1/introduction.xml 2007-04-25 09:14:46 UTC (rev 6176)
+++ trunk/refman-5.1/introduction.xml 2007-04-25 10:19:36 UTC (rev 6177)
Changed blocks: 1, Lines Added: 2, Lines Deleted: 1; 578 bytes
@@ -116,7 +116,8 @@
<para>
For tips on porting the MySQL Database Software to new
architectures or operating systems, see
- <xref linkend="porting"/>.
+ <ulink url="http://forge.mysql.com/wiki/MySQL_Internals_Porting">MySQL
+ Internals: Porting</ulink>.
</para>
</listitem>
Modified: trunk/refman-5.1/language-structure.xml
===================================================================
--- trunk/refman-5.1/language-structure.xml 2007-04-25 09:14:46 UTC (rev 6176)
+++ trunk/refman-5.1/language-structure.xml 2007-04-25 10:19:36 UTC (rev 6177)
Changed blocks: 5, Lines Added: 10, Lines Deleted: 10; 2357 bytes
@@ -1027,11 +1027,11 @@
expression <literal>1e + 3</literal> or as the number
<literal>1e+3</literal>.
</para>
-
+
<para>
A user variable cannot be used directly in an SQL statement as an
- identifier or as part of an identifier. See
- <xref linkend="user-variables"/>, for more information and
+ identifier or as part of an identifier. See
+ <xref linkend="user-variables"/>, for more information and
examples of workarounds.
</para>
@@ -2376,12 +2376,12 @@
variable to <literal>0</literal>, <literal>0.0</literal>, or
<literal>''</literal> to define its type before you use it.
</para>
-
+
<para>
A user variable cannot be used directly in an SQL statement as an
identifier or as part of an identifier, even if it is set off with
backticks. This is shown in the following example:
-
+
<programlisting>
mysql> <userinput>SELECT c1 FROM t;</userinput>
+----+
@@ -2418,10 +2418,10 @@
+------+
1 row in set (0.00 sec)
</programlisting>
-
+
One way to work around this problem is to assemble a string for
the query in application code, as shown here using PHP 5:
-
+
<programlisting>
<?php
$mysqli = new mysqli("localhost", "user", "pass", "test");
@@ -2445,13 +2445,13 @@
$mysqli->close();
?>
</programlisting>
-
+
(Assembling an SQL statement in this fashion is sometimes known as
<quote>Dynamic SQL</quote>.) It is also possible to perform such
operations using prepared statements, without the need to
concatenate strings of SQL in client code. This example
illustrates how this can be done:
-
+
<programlisting>
mysql> <userinput>SET @c = "c1";</userinput>
Query OK, 0 rows affected (0.00 sec)
@@ -2476,7 +2476,7 @@
mysql> <userinput>DEALLOCATE PREPARE stmt;</userinput>
Query OK, 0 rows affected (0.00 sec)
</programlisting>
-
+
You cannot use a placeholder for the name of a database, table, or
column in an SQL prepared statement. See <xref linkend="sqlps"/>,
for more information.
Modified: trunk/refman-5.1/mysql-cluster.xml
===================================================================
--- trunk/refman-5.1/mysql-cluster.xml 2007-04-25 09:14:46 UTC (rev 6176)
+++ trunk/refman-5.1/mysql-cluster.xml 2007-04-25 10:19:36 UTC (rev 6177)
Changed blocks: 2, Lines Added: 2, Lines Deleted: 2; 766 bytes
@@ -6439,7 +6439,7 @@
to define at least <literal>NodeId1</literal>,
<literal>NodeId2</literal>, and the parameters to change.
</para>
-
+
<important>
<para>
Any <literal>[TCP]</literal> sections in the
@@ -6451,7 +6451,7 @@
management server.
</para>
</important>
-
+
<para>
It is also possible to change the default values for these
parameters by setting them in the <literal>[TCP
Modified: trunk/refman-5.1/partitioning.xml
===================================================================
--- trunk/refman-5.1/partitioning.xml 2007-04-25 09:14:46 UTC (rev 6176)
+++ trunk/refman-5.1/partitioning.xml 2007-04-25 10:19:36 UTC (rev 6177)
Changed blocks: 1, Lines Added: 10, Lines Deleted: 10; 1620 bytes
@@ -204,25 +204,25 @@
non-constant and non-random. It may not contain any queries, but
may use an SQL expression that is valid in MySQL, as long as that
expression returns either <literal>NULL</literal> or an integer
- <replaceable>intval</replaceable> such that
-
+ <replaceable>intval</replaceable> such that
+
<programlisting>
-MAXVALUE < <replaceable>intval</replaceable> < MAXVALUE
</programlisting>
-
+
(<literal>MAXVALUE</literal> is used to represent the greatest
possible positive integer.) There are some additional restrictions
- on partitioning functions; see
+ on partitioning functions; see
<xref linkend="partitioning-limitations"/>, for more information
about these.
</para>
-
+
<para>
- Examples of partitioning functions can
- be found in the discussions of partitioning types later in this
- chapter (see <xref linkend="partitioning-types"/>), as well as in
- the partitioning syntax descriptions given in
- <xref linkend="create-table"/>.
+ Examples of partitioning functions can be found in the discussions
+ of partitioning types later in this chapter (see
+ <xref linkend="partitioning-types"/>), as well as in the
+ partitioning syntax descriptions given in
+ <xref linkend="create-table"/>.
</para>
<para>
Modified: trunk/refman-5.1/se-myisam.xml
===================================================================
--- trunk/refman-5.1/se-myisam.xml 2007-04-25 09:14:46 UTC (rev 6176)
+++ trunk/refman-5.1/se-myisam.xml 2007-04-25 10:19:36 UTC (rev 6177)
Changed blocks: 1, Lines Added: 2, Lines Deleted: 1; 668 bytes
@@ -1045,7 +1045,8 @@
occurred during normal operation. This is a bug. You should try
to create a reproducible test case that demonstrates the
problem. See <xref linkend="crashing"/>, and
- <xref linkend="reproducible-test-case"/>.
+ <ulink url="http://forge.mysql.com/wiki/MySQL_Internals_Porting">MySQL
+ Internals: Porting</ulink>.
</para>
<formalpara role="mnmas">
Modified: trunk/refman-5.1/storage-engines.xml
===================================================================
--- trunk/refman-5.1/storage-engines.xml 2007-04-25 09:14:46 UTC (rev 6176)
+++ trunk/refman-5.1/storage-engines.xml 2007-04-25 10:19:36 UTC (rev 6177)
Changed blocks: 1, Lines Added: 4, Lines Deleted: 1; 868 bytes
@@ -894,7 +894,10 @@
<para>
For more information on developing a customer storage engine
that can be used with the Pluggable Storage Engine Architecture,
- see <ulink url="http://forge.mysql.com/wiki/MySQL_Internals_Custom_Engine">Writing a Custom Storage Engine</ulink> on <ulink url="http://forge.mysql.com/wiki">MySQL Forge</ulink>.
+ see
+ <ulink url="http://forge.mysql.com/wiki/MySQL_Internals_Custom_Engine">Writing
+ a Custom Storage Engine</ulink> on
+ <ulink url="http://forge.mysql.com/wiki">MySQL Forge</ulink>.
</para>
</section>
Modified: trunk/refman-5.1/triggers.xml
===================================================================
--- trunk/refman-5.1/triggers.xml 2007-04-25 09:14:46 UTC (rev 6176)
+++ trunk/refman-5.1/triggers.xml 2007-04-25 10:19:36 UTC (rev 6177)
Changed blocks: 1, Lines Added: 2, Lines Deleted: 2; 611 bytes
@@ -733,8 +733,8 @@
</para>
<remark role="todo">
- [js] Add an example demonstrating a multiple-table insert, since we
- now link to this section from a FAQ question concerning these.
+ [js] Add an example demonstrating a multiple-table insert, since
+ we now link to this section from a FAQ question concerning these.
</remark>
<para>
Modified: trunk/refman-5.1/tutorial.xml
===================================================================
--- trunk/refman-5.1/tutorial.xml 2007-04-25 09:14:46 UTC (rev 6176)
+++ trunk/refman-5.1/tutorial.xml 2007-04-25 10:19:36 UTC (rev 6177)
Changed blocks: 3, Lines Added: 8, Lines Deleted: 8; 1964 bytes
@@ -2822,13 +2822,13 @@
| pet |
+---------------------+
</programlisting>
-
+
<para>
The name of the column in the output produced by this statement is
always
<literal>Tables_in_<replaceable>db_name</replaceable></literal>,
where <replaceable>db_name</replaceable> is the name of the
- database. See <xref linkend="show-tables"/>, for more information.
+ database. See <xref linkend="show-tables"/>, for more information.
</para>
<para>
@@ -2850,7 +2850,7 @@
| death | date | YES | | NULL | |
+---------+-------------+------+-----+---------+-------+
</programlisting>
-
+
<para>
<literal>Field</literal> indicates the column name,
<literal>Type</literal> is the data type for the column,
@@ -2860,22 +2860,22 @@
specifies the column's default value. <literal>Extra</literal>
displays special information about columns; for example, if a
column was created with the <literal>AUTO_INCREMENT</literal>
- option, this is shown here.
+ option, this is shown here.
</para>
-
+
<para>
<literal>DESC</literal> is a short form of
<literal>DESCRIBE</literal>. See <xref linkend="describe"/>, for
more information.
</para>
-
+
<para>
You can obtain the <literal>CREATE TABLE</literal> statement
necessary to create an existing table using the <literal>SHOW
- CREATE TABLE</literal> statement. See
+ CREATE TABLE</literal> statement. See
<xref linkend="show-create-table"/>.
</para>
-
+
<para>
If you have indexes on a table, <literal>SHOW INDEX FROM
<replaceable>tbl_name</replaceable></literal> produces information
Modified: trunk/refman-common/bug-reports.xml
===================================================================
--- trunk/refman-common/bug-reports.xml 2007-04-25 09:14:46 UTC (rev 6176)
+++ trunk/refman-common/bug-reports.xml 2007-04-25 10:19:36 UTC (rev 6177)
Changed blocks: 2, Lines Added: 2, Lines Deleted: 2; 1037 bytes
@@ -196,7 +196,7 @@
everything you did that led to the problem and describe, in exact
detail, the problem itself. The best reports are those that include
a full example showing how to reproduce the bug or problem. See
- <xref linkend="reproducible-test-case"/>.
+<ulink url="http://forge.mysql.com/wiki/MySQL_Internals_Porting">MySQL Internals: Porting</ulink>.
</para>
<para>
@@ -328,7 +328,7 @@
usually get this information by running
<command>mysqld</command> with query logging enabled, and then
looking in the log after <command>mysqld</command> crashes. See
- <xref linkend="using-log-files"/>.
+<ulink url="http://forge.mysql.com/wiki/MySQL_Internals_Porting">MySQL Internals: Porting</ulink>.
</para>
</listitem>
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r6177 - in trunk: refman-4.1 refman-5.0 refman-5.1 refman-common | mcbrown | 25 Apr |
