Below is the list of changes that have just been committed into a local
mysqldoc repository of jon. When jon does a push these changes will
be propagated to the main repository and, within 24 hours after the
push, to the public repository.
For information on how to access the public repository
see http://www.mysql.com/doc/I/n/Installing_source_tree.html
ChangeSet
1.2924 05/07/02 04:59:02 jon@stripped +2 -0
mysql-database-administration.xml: Started removal
of pre-5.0 material from chapter.
ndbcluster.xml: Minor fix in wording.
refman-5.0/ndbcluster.xml
1.8 05/07/02 04:58:39 jon@stripped +3 -3
Fixed confusing multiple use of "disabled".
refman-5.0/mysql-database-administration.xml
1.9 05/07/02 04:58:39 jon@stripped +292 -429
Remove pre-5.0 references from chapter.
# This is a BitKeeper patch. What follows are the unified diffs for the
# set of deltas contained in the patch. The rest of the patch, the part
# that BitKeeper cares about, is below these diffs.
# User: jon
# Host: gigan.site
# Root: /home/jon/bk/mysqldoc
--- 1.8/refman-5.0/mysql-database-administration.xml 2005-07-01 21:47:49 +10:00
+++ 1.9/refman-5.0/mysql-database-administration.xml 2005-07-02 04:58:39 +10:00
@@ -294,7 +294,7 @@
<para>
You can find the MySQL-Max binaries on the MySQL AB Web site at
- <ulink url="http://dev.mysql.com/downloads/mysql-4.0.html">http://dev.mysql.com/downloads/mysql-4.0.html</ulink>.
+ <ulink url="http://dev.mysql.com/downloads/">http://dev.mysql.com/downloads/</ulink>.
</para>
<para>
@@ -319,10 +319,10 @@
<para>
This option enables support for the InnoDB storage engine.
- MySQL-Max servers always include InnoDB support, but this option
- actually is needed only for MySQL 3.23. From MySQL 4 onwards,
- InnoDB is included by default in binary distributions, so you do
- not need a MySQL-Max server merely to obtain InnoDB support.
+ MySQL-Max servers always include InnoDB support. From MySQL 4.0
+ onwards, InnoDB is included by default in all binary distributions,
+ so you do not need a MySQL-Max server merely to obtain InnoDB
+ support.
</para></listitem>
<listitem><para>
@@ -340,9 +340,9 @@
<para>
This define is enabled to turn on database symbolic link support
- for Windows. (This applies only before MySQL 4.0. As of MySQL 4.0,
- symbolic link support is available for all Windows servers, so a
- Max server is not needed to take advantage of this feature.)
+ for Windows. In MySQL 5.0, symbolic link support is available
+ for all Windows servers, so a Max server is not needed to take
+ advantage of this feature.
</para></listitem>
<listitem><para>
@@ -350,9 +350,11 @@
</para>
<para>
- This option enables support for the NDB Cluster storage engine in
- MySQL 4.1.2 and newer. Note that as of MySQL 5.0.3, CLuster is
- supported on Linux, Solaris, and Mac OS X only.
+ This option enables support for the NDB Cluster storage engine.
+ Currently (as of ¤t-version;), Cluster is supported on Linux,
+ Solaris, and Mac OS X only. Some users have reported success in
+ using MySQL Cluster built from source on BSD operating systems,
+ but these are not officially supported at this time.
</para></listitem>
</itemizedlist>
@@ -380,8 +382,8 @@
</para>
<para>
- The following table shows on which platforms allow MySQL-Max
- binaries include support for BDB and/or NDB Cluster:
+ The following table shows on which platforms MySQL-Max binaries
+ include support for BDB and/or NDB Cluster:
</para>
<informaltable>
@@ -537,7 +539,7 @@
</tgroup>
</informaltable>
-<!-- Output for both SHOW commands following is from 5.0.2-alpha-nt-max -->
+<!-- Output for both SHOW commands following is from 5.0.7-alpha-nt-max -->
<para>
To find out which storage engines your server supports, issue the
@@ -546,27 +548,29 @@
<programlisting>
mysql> SHOW ENGINES;
-+------------+---------+------------------------------------------------------------+
-| Engine | Support | Comment |
-+------------+---------+------------------------------------------------------------+
-| MyISAM | DEFAULT | Default engine as of MySQL 3.23 with great performance |
-| HEAP | YES | Alias for MEMORY |
-| MEMORY | YES | Hash based, stored in memory, useful for temporary tables |
-| MERGE | YES | Collection of identical MyISAM tables |
-| MRG_MYISAM | YES | Alias for MERGE |
-| ISAM | NO | Obsolete storage engine, now replaced by MyISAM |
-| MRG_ISAM | NO | Obsolete storage engine, now replaced by MERGE |
-| InnoDB | YES | Supports transactions, row-level locking, and foreign keys |
-| INNOBASE | YES | Alias for INNODB |
-| BDB | YES | Supports transactions and page-level locking |
-| BERKELEYDB | YES | Alias for BDB |
-| NDBCLUSTER | NO | Clustered, fault-tolerant, memory-based tables |
-| NDB | NO | Alias for NDBCLUSTER |
-| EXAMPLE | NO | Example storage engine |
-| ARCHIVE | NO | Archive storage engine |
-| CSV | NO | CSV storage engine |
-+------------+---------+------------------------------------------------------------+
-16 rows in set (0.02 sec)
++------------+---------+----------------------------------------------------------------+
+| Engine | Support | Comment |
++------------+---------+----------------------------------------------------------------+
+| MyISAM | DEFAULT | Default engine as of MySQL 3.23 with great performance |
+| MEMORY | YES | Hash based, stored in memory, useful for temporary tables |
+| HEAP | YES | Alias for MEMORY |
+| MERGE | YES | Collection of identical MyISAM tables |
+| MRG_MYISAM | YES | Alias for MERGE |
+| ISAM | NO | Obsolete storage engine, now replaced by MyISAM |
+| MRG_ISAM | NO | Obsolete storage engine, now replaced by MERGE |
+| InnoDB | YES | Supports transactions, row-level locking, and foreign keys |
+| INNOBASE | YES | Alias for INNODB |
+| BDB | YES | Supports transactions and page-level locking |
+| BERKELEYDB | YES | Alias for BDB |
+| NDBCLUSTER | NO | Clustered, fault-tolerant, memory-based tables |
+| NDB | NO | Alias for NDBCLUSTER |
+| EXAMPLE | NO | Example storage engine |
+| ARCHIVE | YES | Archive storage engine |
+| CSV | NO | CSV storage engine |
+| FEDERATED | YES | Federated MySQL storage engine |
+| BLACKHOLE | YES | /dev/null storage engine (anything you write to it disappears) |
++------------+---------+----------------------------------------------------------------+
+18 rows in set (0.00 sec)
</programlisting>
<para>
@@ -580,27 +584,29 @@
</para>
<programlisting>
-mysql> SHOW VARIABLES LIKE 'have_%';
-+---------------------+-------+
-| Variable_name | Value |
-+---------------------+-------+
-| have_archive | NO |
-| have_bdb | YES |
-| have_compress | YES |
-| have_crypt | NO |
-| have_csv | NO |
-| have_example_engine | NO |
-| have_geometry | YES |
-| have_innodb | YES |
-| have_isam | NO |
-| have_ndbcluster | NO |
-| have_openssl | NO |
-| have_query_cache | YES |
-| have_raid | NO |
-| have_rtree_keys | YES |
-| have_symlink | YES |
-+---------------------+-------+
-15 rows in set (0.15 sec)
+mysql> SHOW VARIABLES LIKE 'have%';
++-----------------------+-------+
+| Variable_name | Value |
++-----------------------+-------+
+| have_archive | YES |
+| have_bdb | YES |
+| have_blackhole_engine | YES |
+| have_compress | YES |
+| have_crypt | NO |
+| have_csv | NO |
+| have_example_engine | NO |
+| have_federated_engine | YES |
+| have_geometry | YES |
+| have_innodb | YES |
+| have_isam | NO |
+| have_ndbcluster | NO |
+| have_openssl | YES |
+| have_query_cache | YES |
+| have_raid | NO |
+| have_rtree_keys | YES |
+| have_symlink | YES |
++-----------------------+-------+
+17 rows in set (0.06 sec)
</programlisting>
<para>
@@ -719,12 +725,11 @@
</para>
<para>
- <emphasis role="bold">Note</emphasis>: Before MySQL 4.0,
- <command>mysqld_safe</command> is named
- <command>safe_mysqld</command>. To preserve backward compatibility,
- MySQL binary distributions for some time will include
- <command>safe_mysqld</command> as a symbolic link to
- <command>mysqld_safe</command>.
+ <emphasis role="bold">Note</emphasis>: To preserve backward
+ compatibility with older versions of MySQL, MySQL binary
+ distributions still include <command>safe_mysqld</command> as a
+ symbolic link to <command>mysqld_safe</command>. However, you should
+ not rely on this as it almost certainly will be removed in future.
</para>
<para>
@@ -786,8 +791,8 @@
<literal>[mysqld_safe]</literal> sections in option files. For
backward compatibility, it also reads
<literal>[safe_mysqld]</literal> sections, although you should
- rename such sections to <literal>[mysqld_safe]</literal> when you
- begin using MySQL 4.0 or later.
+ rename such sections to <literal>[mysqld_safe]</literal> in MySQL
+ 5.0.
</para>
<para>
@@ -803,7 +808,7 @@
</para>
<para>
- Display a help message and exit. (New in 5.0.3)
+ Display a help message and exit. (Added in MySQL 5.0.3)
</para></listitem>
<listitem><para>
@@ -851,15 +856,6 @@
</para></listitem>
<listitem><para>
- <literal>--err-log=<replaceable>path</replaceable></literal>
- </para>
-
- <para>
- The old form of the <literal>--log-error</literal> option, to be
- used before MySQL 4.0.
- </para></listitem>
-
- <listitem><para>
<literal>--ledir=<replaceable>path</replaceable></literal>
</para>
@@ -912,8 +908,7 @@
<para>
Use the <literal>nice</literal> program to set the server's
- scheduling priority to the given value. This option was added in
- MySQL 4.0.14.
+ scheduling priority to the given value.
</para></listitem>
<listitem><para>
@@ -1069,8 +1064,7 @@
</para></listitem>
<listitem><para>
- Runs a check on <literal>MyISAM</literal> and
- <literal>ISAM</literal> tables.
+ Runs a check on <literal>MyISAM</literal> tables.
</para></listitem>
<listitem><para>
@@ -1144,8 +1138,8 @@
<literal>[mysql.server]</literal> and <literal>[mysqld]</literal>
sections of option files. (For backward compatibility, it also reads
<literal>[mysql_server]</literal> sections, although you should
- rename such sections to <literal>[mysql.server]</literal> when you
- begin using MySQL 4.0 or later.)
+ rename such sections to <literal>[mysql.server]</literal> when using
+ MySQL 5.0.)
</para>
</section>
@@ -1414,7 +1408,7 @@
</para>
<para>
- Disable warnings. This option was added in MySQL 4.1.6.
+ Disable warnings.
</para>
<para>
@@ -1465,7 +1459,7 @@
</para>
<para>
- Be more verbose. This option was added in MySQL 4.1.6.
+ Be more verbose.
</para>
<para>
@@ -1585,7 +1579,7 @@
servers with the same data directory. Use separate data
directories, unless you <emphasis>know</emphasis> what you are
doing. Starting multiple servers with the same data directory
- <emphasis>does not</emphasis> give you extra performance in a
+ does <emphasis>not</emphasis> give you extra performance in a
threaded system. See <xref linkend="multiple-servers"/>.
</para></listitem>
@@ -1658,21 +1652,20 @@
<title id='title-instance-manager'>&title-instance-manager;</title>
<para>
- This section discusses use of the MySQL Instance Manager. MySQL
- Instance Manager (IM) is a daemon running on a TCP/IP port, which
- serves for monitoring and management of MySQL Database Server
- instances. MySQL Instance Manager is currently available for
- unix-like operating systems.
+ This section discusses the use of the MySQL Instance Manager (IM).
+ This is a daemon running on a TCP/IP port, which provides monitoring
+ and management of MySQL Database Server instances. MySQL Instance
+ Manager is currently available for unix-like operating systems.
</para>
<para>
MySQL Instance Manager is included in MySQL distributions from
- version 5.0.3. MySQL Instance Manager can be used to start and stop
- the MySQL Server, <emphasis role="bold">even from a remote
- host</emphasis>, instead of the mysqld_safe script. MySQL Instance
- Manager also implements the functionality (and most of the syntax) of
- the <command>mysqld_multi</command> script. A more detailed
- description of the MySQL Instance Manager follows.
+ version 5.0.3, and can be used in place of the
+ <literal>mysqld_safe</literal> script to start and stop the MySQL
+ Server, <emphasis role="bold">even from a remote host</emphasis>.
+ MySQL Instance Manager also implements the functionality (and most of
+ the syntax) of the <command>mysqld_multi</command> script. A more
+ detailed description of MySQL Instance Manager follows.
</para>
<section id="instance-manager-startup-process">
@@ -1684,27 +1677,33 @@
<command>mysql.server</command> script, which usually resides in the
<literal>/etc/init.d/</literal> folder. In MySQL 5.0.3 this script
invokes <command>mysqlmanager</command> (the MySQL Instance Manager
- binary) to start MySQL. In prior versions of MySQL the
- <command>mysqld_safe</command> script is used for this purpose.
+ binary) to start MySQL. (In prior versions of MySQL the
+ <command>mysqld_safe</command> script is used for this purpose.)
Starting from MySQL 5.0.4 the behaviour of the init script was
- changed again to incorporate both setup schemes. In 5.0.4 the init
- startup script uses the old scheme (invoking
+ changed again to incorporate both setup schemes. In version 5.0.4,
+ the init startup script uses the old scheme (invoking
<command>mysqld_safe</command>) by default, but one can set the
<literal>use_mysqld_safe</literal> variable in the script to
<literal>0</literal> (zero) to use the MySQL Instance Manager to
start a server.
</para>
+<!--
+ TODO: Which "default" location? /usr/local/mysql/bin (RPM),
+ /usr/sbin (tarfile), /usr/local/bin (source), or
+ /usr/local/mysql/libexec (also commonly used)?
+-->
+
<para>
- Instance Manager behaviour in this case depends on the options given
- in the MySQL configuration file. If there is no configuration file,
- the MySQL Instance Manager creates an instance named
+ The Instance Manager's behaviour in this case depends on the options
+ given in the MySQL configuration file. If there is no configuration
+ file, the MySQL Instance Manager creates an instance named
<literal>mysqld</literal> and attempts to start it with default
(compiled-in) configuration values. This means that the IM cannot
guess the placement of <command>mysqld</command> if it is not
installed in the default location. If you have installed the MySQL
server in a non-standard location you should use a configuration
- file.
+ file. See <xref linkend="installation-layouts"/>.
</para>
<para>
@@ -1717,12 +1716,12 @@
</para>
<para>
- Note that there is a special option which is recognized only by the
- IM called <literal>mysqld-path</literal> (<literal>mysqld-path =
- <path-to-mysqld-binary></literal>). Use this variable to let
- the IM know where the mysqld binary resides. You should also set
- <literal>basedir</literal> and <literal>datadir</literal> options
- for the server.
+ Note that there is a special option <literal>mysqld-path</literal>
+ (<literal>mysqld-path = <path-to-mysqld-binary></literal>)
+ which is recognized only by the IM. Use this variable to let the IM
+ know where <literal>mysqld</literal> binary resides. You should
+ also set <literal>basedir</literal> and <literal>datadir</literal>
+ options for the server.
</para>
<para>
@@ -1763,9 +1762,9 @@
Communication with the MySQL Instance Manager is handled using the
MySQL client-server protocol. As such, you can connect to the IM
using the standard <command>mysql</command> client program, as well
- as the MySQL C API. The IM supports the new version of the MySQL
- client-server protocol, so one should use client tools and libraries
- distributed along with mysql-4.1 or later.
+ as the MySQL C API. The IM supports the version of the MySQL
+ client-server protocol used by the client tools and libraries
+ distributed along with mysql-4.1 or later.
</para>
<para>
@@ -1786,7 +1785,7 @@
To generate such an entry one should invoke IM with the
<command>--passwd</command> option. Then the output can be
redirected to the <filename>/etc/mysqlmanager.passwd</filename> file
- to add a new user. The sample command is given below.
+ to add a new user. A sample command is given below.
</para>
<programlisting>
@@ -1902,8 +1901,8 @@
<para>
Where to look for MySQL Server binary, if no path was provided in
- the instance section. E.g. <literal>default-mysqld-path =
- /usr/sbin/mysqld</literal>
+ the instance section. Example: <literal>default-mysqld-path =
+ /usr/sbin/mysqld</literal>.
</para></listitem>
<listitem><para>
@@ -2001,9 +2000,10 @@
<para>
A number of seconds IM should wait for the instance to shut down.
- Default time is 35 seconds. After the delay expires, the IM assumes
- that the instance is hanging and attempts to kill -9 it. If you use
- InnoDB with large tables, you should increase this value.
+ The default is 35 seconds. After the delay expires, the IM assumes
+ that the instance is hanging and attempts to <literal>kill
+ -9</literal> it. If you use InnoDB with large tables, you should
+ increase this value.
</para></listitem>
<listitem><para>
@@ -2074,7 +2074,7 @@
<para>
<programlisting>
-mysql> start instance mysqld4;
+mysql> START INSTANCE mysqld4;
Query OK, 0 rows affected (0,00 sec)
</programlisting>
</para></listitem>
@@ -2089,7 +2089,7 @@
<para>
<programlisting>
-mysql> stop instance mysqld4;
+mysql> STOP INSTANCE mysqld4;
Query OK, 0 rows affected (0,00 sec)
</programlisting>
</para></listitem>
@@ -2126,7 +2126,7 @@
<para>
<programlisting>
-mysql> show instance status mysqld3;
+mysql> SHOW INSTANCE STATUS mysqld3;
+---------------+--------+---------+
| instance_name | status | version |
+---------------+--------+---------+
@@ -2146,7 +2146,7 @@
<para>
<programlisting>
-mysql> show instance options mysqld3;
+mysql> SHOW INSTANCE OPTIONS mysqld3;
+---------------+---------------------------------------------------+
| option_name | value |
+---------------+---------------------------------------------------+
@@ -2178,7 +2178,7 @@
<para>
<programlisting>
-mysql> show mysqld log files;
+mysql> SHOW mysqld LOG FILES;
+-------------+------------------------------------+----------+
| Logfile | Path | Filesize |
+-------------+------------------------------------+----------+
@@ -2208,7 +2208,7 @@
<para>
<programlisting>
-mysql> show mysqld log general 21, 2;
+mysql> SHOW mysqld LOG GENERAL 21, 2;
+---------------------+
| Log |
+---------------------+
@@ -2231,7 +2231,7 @@
<para>
<programlisting>
-mysql> set mysqld2.port=3322;
+mysql> SET mysqld2.port=3322;
Query OK, 0 rows affected (0.00 sec)
</programlisting>
</para>
@@ -2254,7 +2254,7 @@
<para>
<programlisting>
-mysql> unset mysqld2.port;
+mysql> UNSET mysqld2.port;
Query OK, 0 rows affected (0.00 sec)
</programlisting>
</para>
@@ -2279,7 +2279,7 @@
<para>
<programlisting>
-mysql> flush instances;
+mysql> FLUSH INSTANCES;
Query OK, 0 rows affected (0.04 sec)
</programlisting>
</para></listitem>
@@ -2295,7 +2295,7 @@
<title id='title-configuring-mysql'>&title-configuring-mysql;</title>
<para>
- This section discusses MySQL server configuration topics:
+ This section discusses these MySQL server configuration topics:
</para>
<itemizedlist>
@@ -2363,10 +2363,8 @@
<para>
<command>mysqld</command> accepts many command-line options. For a
- list, execute <command>mysqld --help</command>. Before MySQL 4.1.1,
- <literal>--help</literal> prints the full help message. As of 4.1.1,
- it prints a brief message; to see the full list, use <command>mysqld
- --verbose --help</command>.
+ brief list, execute <command>mysqld --help</command>. To see the
+ full list, use <command>mysqld --verbose --help</command>.
</para>
<para>
@@ -2396,7 +2394,7 @@
<listitem><para>
Options specific to particular storage engines: See
- <xref linkend="myisam-start"/>, <xref linkend="bdb-start"/>,
+ <xref linkend="myisam-start"/>, <xref linkend="bdb-start"/>, and
<xref linkend="innodb-start"/>.
</para></listitem>
@@ -2414,9 +2412,7 @@
</para>
<para>
- Display a short help message and exit. Before MySQL 4.1.1,
- <literal>--help</literal> displays the full help message. As of
- 4.1.1, it displays an abbreviated message only. Use both the
+ Display a short help message and exit. Use both the
<literal>--verbose</literal> and <literal>--help</literal> options
to see the full message.
</para></listitem>
@@ -2431,8 +2427,9 @@
loaded. By default, the option is off and only UDFs that have at
least one auxiliary symbol can be loaded. This prevents attempts at
loading functions from shared object files other than those
- containing legitimate UDFs. This option was added in MySQL 4.0.24,
- 4.1.10a, and 5.0.3. See <xref linkend="udf-security"/>.
+ containing legitimate UDFs. In the MySQL 5.0 series of releases,
+ this option was added in version 5.0.3. See
+ <xref linkend="udf-security"/>.
</para></listitem>
<listitem><para>
@@ -2440,7 +2437,7 @@
</para>
<para>
- Use standard SQL syntax instead of MySQL syntax. See
+ Use standard (ANSI) SQL syntax instead of MySQL syntax. See
<xref linkend="ansi-mode"/>. For more precise control over the
server SQL mode, use the <literal>--sql-mode</literal> option
instead.
@@ -2455,9 +2452,14 @@
The path to the MySQL installation directory. All paths are usually
resolved relative to this.
</para></listitem>
-
+
+ <!--
+ TODO: Cut this? If not, remove space in "- -big-tables" which
+ was added to prevent XML parse error.
+ -->
+<!--
<listitem><para>
- <literal>--big-tables</literal>
+ <literal>- -big-tables</literal>
</para>
<para>
@@ -2468,7 +2470,8 @@
automatically by using memory for small temporary tables and
switching to disk tables where necessary.
</para></listitem>
-
+-->
+
<listitem><para>
<literal>--bind-address=<replaceable>IP</replaceable></literal>
</para>
@@ -2482,10 +2485,10 @@
</para>
<para>
- Write the error log messages to stderr/stdout even if
- <literal>--log-error</literal> is specified. On Windows,
- <command>mysqld</command> does not close the console screen if this
- option is used.
+ Write error log messages to <literal>stderr</literal> and
+ <literal>stdout</literal> even if <literal>--log-error</literal>
+ is specified. On Windows, <command>mysqld</command> does not close
+ the console screen if this option is used.
</para></listitem>
<listitem><para>
@@ -2504,11 +2507,9 @@
<para>
Put the <command>mysqld</command> server in a closed environment
during startup by using the <literal>chroot()</literal> system
- call. This is a recommended security measure as of MySQL 4.0.
- (MySQL 3.23 is not able to provide a <literal>chroot()</literal>
- jail that is 100% closed.) Note that use of this option somewhat
- limits <literal>LOAD DATA INFILE</literal> and <literal>SELECT ...
- INTO OUTFILE</literal>.
+ call. This is a recommended security measure. Note that use of this
+ option somewhat limits <literal>LOAD DATA INFILE</literal> and
+ <literal>SELECT ... INTO OUTFILE</literal>.
</para></listitem>
<listitem><para>
@@ -2517,8 +2518,7 @@
<para>
Use <replaceable>charset</replaceable> as the default server
- character set. This option is available as of MySQL 4.1.3. See
- <xref linkend="character-sets"/>.
+ character set. See <xref linkend="character-sets"/>.
</para></listitem>
<listitem><para>
@@ -2540,8 +2540,7 @@
<para>
Use <replaceable>collation</replaceable> as the default server
- collation. This option is available as of MySQL 4.1.3. See
- <xref linkend="character-sets"/>.
+ collation. See <xref linkend="character-sets"/>.
</para></listitem>
<listitem><para>
@@ -2568,13 +2567,13 @@
</para></listitem>
<listitem><para>
- <literal>--default-character-set=<replaceable>charset</replaceable></literal>
+ (<emphasis>DEPRECATED</emphasis>) <literal>--default-character-set=<replaceable>charset</replaceable></literal>
</para>
<para>
Use <replaceable>charset</replaceable> as the default character
set. This option is deprecated in favor of
- <literal>--character-set-server</literal> as of MySQL 4.1.3. See
+ <literal>--character-set-server</literal>. See
<xref linkend="character-sets"/>.
</para></listitem>
@@ -2585,7 +2584,7 @@
<para>
Use <replaceable>collation</replaceable> as the default collation.
This option is deprecated in favor of
- <literal>--collation-server</literal> as of MySQL 4.1.3. See
+ <literal>--collation-server</literal>. See
<xref linkend="character-sets"/>.
</para></listitem>
@@ -2595,8 +2594,7 @@
<para>
This option is a synonym for
- <literal>--default-table-type</literal>. It is available as of
- MySQL 4.1.2.
+ <literal>--default-table-type</literal>.
</para></listitem>
<listitem><para>
@@ -2617,7 +2615,7 @@
<literal>time_zone</literal> system variable. If this option is not
given, the default time zone is the same as the system time zone
(given by the value of the <literal>system_time_zone</literal>
- system variable. This option is available as of MySQL 4.1.3.
+ system variable.
</para></listitem>
<listitem><para>
@@ -2631,9 +2629,8 @@
disables delayed key writes. <literal>ON</literal> enables delayed
key writes for those tables that were created with the
<literal>DELAYED KEYS</literal> option. <literal>ALL</literal>
- delays key writes for all <literal>MyISAM</literal> tables.
- Available as of MySQL 4.0.3. See
- <xref linkend="server-parameters"/>. See
+ delays key writes for all <literal>MyISAM</literal> tables. See
+ <xref linkend="server-parameters"/>. See
<xref linkend="myisam-start"/>.
</para>
@@ -2646,16 +2643,6 @@
</para></listitem>
<listitem><para>
- <literal>--delay-key-write-for-all-tables</literal>
- </para>
-
- <para>
- Old form of <literal>--delay-key-write=ALL</literal> for use prior
- to MySQL 4.0.3. As of 4.0.3, use
- <literal>--delay-key-write</literal> instead.
- </para></listitem>
-
- <listitem><para>
<literal>--des-key-file=<replaceable>file_name</replaceable></literal>
</para>
@@ -2683,7 +2670,7 @@
<para>
This is a bit mask of different flags you can use for debugging the
<command>mysqld</command> server. Do not use this option unless you
- know exactly what it does!
+ know <emphasis>exactly</emphasis> what it does!
</para></listitem>
<listitem><para>
@@ -2864,20 +2851,16 @@
</para></listitem>
<listitem><para>
- <literal>--log-long-format</literal>
+ (<emphasis>DEPRECATED</emphasis>) <literal>--log-long-format</literal>
</para>
<para>
- Log some extra information to the log files (update log, binary
- update log, and slow queries log, whatever log has been activated).
- For example, username and timestamp are logged for queries. Before
- MySQL 4.1, if you are using <literal>--log-slow-queries</literal>
- and <literal>--log-long-format</literal>, queries that are not
- using indexes also are logged to the slow query log.
- <literal>--log-long-format</literal> is deprecated as of MySQL
- version 4.1, when <literal>--log-short-format</literal> was
- introduced. (Long log format is the default setting since version
- 4.1.) Also note that starting with MySQL 4.1, the
+ Log extra information to whichever of the update log, binary update
+ log, and slow queries log that have been activated. For example,
+ username and timestamp are logged for all queries. This option is
+ deprecated in MySQL 5.0, as it now represents the default logging
+ behaviour. (See the description for
+ <literal>--log-short-format</literal>.) The
<literal>--log-queries-not-using-indexes</literal> option is
available for the purpose of logging queries that do not use
indexes to the slow query log.
@@ -2890,8 +2873,8 @@
<para>
If you are using this option with
<literal>--log-slow-queries</literal>, then queries that are not
- using indexes also are logged to the slow query log. This option is
- available as of MySQL 4.1. See <xref linkend="slow-query-log"/>.
+ using indexes also are logged to the slow query log. See
+ <xref linkend="slow-query-log"/>.
</para></listitem>
<listitem><para>
@@ -2899,10 +2882,9 @@
</para>
<para>
- Log less information to the log files (update log, binary update
- log, and slow queries log, whatever log has been activated). For
- example, username and timestamp are not logged for queries. This
- option was introduced in MySQL 4.1.
+ Log less information to whichever of the update log, binary update
+ log, and slow queries log that have been activated. For example,
+ the username and timestamp are not logged for queries.
</para></listitem>
<listitem><para>
@@ -2914,11 +2896,7 @@
TABLE</literal>, <literal>ANALYZE TABLE</literal>, and
<literal>ALTER TABLE</literal> to the slow query log.
</para>
-
- <para>
- This option was added in MySQL 4.1.13. (It is unnecessary in MySQL
- 4.0 because slow administrative statements are logged by default.)
- </para></listitem>
+ </listitem>
<listitem><para>
<literal>--log-slow-queries[=<replaceable>file</replaceable>]</literal>
@@ -2927,27 +2905,12 @@
<para>
Log all queries that have taken more than
<literal>long_query_time</literal> seconds to execute to this file.
- See <xref linkend="slow-query-log"/>. Note that the default for the
- amount of information logged has changed in MySQL 4.1. See the
+ See <xref linkend="slow-query-log"/>. See the descriptions of the
<literal>--log-long-format</literal> and
<literal>--log-short-format</literal> options for details.
</para></listitem>
<listitem><para>
- <literal>--log-update[=<replaceable>file</replaceable>]</literal>
- </para>
-
- <para>
- Log updates to <replaceable>file#</replaceable> where
- <replaceable>#</replaceable> is a unique number if not given. See
- <xref linkend="update-log"/>. The update log is deprecated and is
- removed in MySQL 5.0.0; you should use the binary log instead
- (<literal>--log-bin</literal>). See <xref linkend="binary-log"/>.
- Starting from version 5.0.0, using <literal>--log-update</literal>
- turns on the binary log instead (see <xref linkend="news-5-0-0"/>).
- </para></listitem>
-
- <listitem><para>
<literal>--log-warnings, -W</literal>
</para>
@@ -2956,18 +2919,12 @@
to the error log. Enabling this option is recommended, for example,
if you use replication (you get more information about what is
happening, such as messages about network failures and
- reconnections). This option is enabled by default as of MySQL
- 4.0.19 and 4.1.2; to disable it, use
- <literal>--skip-log-warnings</literal>. As of MySQL 4.0.21 and
- 4.1.3, aborted connections are not logged to the error log unless
- the value is greater than 1. See
- <xref linkend="communication-errors"/>.
+ reconnections). This option is enabled by default in MySQL 5.0; to
+ disable it, use <literal>--skip-log-warnings</literal>. Aborted
+ connections are not logged to the error log unless the value is
+ greater than 1. See <xref linkend="communication-errors"/>.
</para>
-
- <para>
- This option was named <literal>--warnings</literal> before MySQL
- 4.0.
- </para></listitem>
+ </listitem>
<listitem><para>
<literal>--low-priority-updates</literal>
@@ -3086,10 +3043,7 @@
even if some rows would be deleted, but it keeps the old data file
as a backup so that you can later examine what happened.
</para>
-
- <para>
- This option is available as of MySQL 3.23.25.
- </para></listitem>
+ </listitem>
<listitem><para>
<literal>--ndb-connectstring=<replaceable>connect_string</replaceable></literal>
@@ -3108,42 +3062,9 @@
<para>
If the binary includes support for the <literal>NDB
- Cluster</literal> storage engine (from version 4.1.3, the MySQL-Max
- binaries are built with <literal>NDB Cluster</literal> enabled) the
- default disabling of support for the <literal>NDB Cluster</literal>
- storage engine can be overruled by using this option. Using the
- <literal>NDB Cluster</literal> storage engine is necessary for
- using MySQL Cluster. See <xref linkend="ndbcluster"/>.
- </para></listitem>
-
- <listitem><para>
- <literal>--new</literal>
- </para>
-
- <para>
- The <literal>--new</literal> option can be used to make the server
- behave as 4.1 in certain respects, easing a 4.0 to 4.1 upgrade:
-
- <itemizedlist>
-
- <listitem><para>
- Hexadecimal strings such as <literal>0xFF</literal> are treated
- as strings by default rather than as numbers. (Works in 4.0.12
- and up.)
- </para></listitem>
-
- <listitem><para>
- <literal>TIMESTAMP</literal> is returned as a string with the
- format <literal>'YYYY-MM-DD HH:MM:SS'</literal>. (Works in 4.0.13
- and up.) See <xref linkend="column-types"/>.
- </para></listitem>
-
- </itemizedlist>
- </para>
-
- <para>
- This option can be used to help you see how your applications
- behave in MySQL 4.1, without actually upgrading to 4.1.
+ Cluster</literal> storage engine, the default disabling of support
+ for MySQL Cluster can be overruled by using this option. See
+ <xref linkend="ndbcluster"/>.
</para></listitem>
<listitem><para>
@@ -3153,7 +3074,7 @@
<para>
Force the server to generate short (pre-4.1) password hashes for
new passwords. This is useful for compatibility when the server
- must support older client programs. See
+ must support older client programs. See
<xref linkend="password-hashing"/>.
</para></listitem>
@@ -3226,17 +3147,11 @@
</para></listitem>
<listitem><para>
- <literal>--safe-show-database</literal>
+ (<emphasis>DEPRECATED</emphasis>) <literal>--safe-show-database</literal>
</para>
<para>
- With this option, the <literal>SHOW DATABASES</literal> statement
- displays only the names of those databases for which the user has
- some kind of privilege. As of MySQL 4.0.2, this option is
- deprecated and doesn't do anything (it is enabled by default),
- because there is a <literal>SHOW DATABASES</literal> privilege that
- can be used to control access to database names on a per-account
- basis. See <xref linkend="privileges-provided"/>.
+ See <xref linkend="privileges-provided"/>.
</para></listitem>
<listitem><para>
@@ -3256,7 +3171,7 @@
<para>
Disallow authentication for accounts that have old (pre-4.1)
- passwords. This option is available as of MySQL 4.1.1.
+ passwords.
</para></listitem>
<listitem><para>
@@ -3265,7 +3180,7 @@
<para>
Enable shared-memory connections by local clients. This option is
- available only on Windows. It was added in MySQL 4.1.0.
+ available only on Windows.
</para></listitem>
<listitem><para>
@@ -3274,7 +3189,7 @@
<para>
The name to use for shared-memory connections. This option is
- available only on Windows. It was added in MySQL 4.1.0.
+ available only on Windows.
</para></listitem>
<listitem><para>
@@ -3298,27 +3213,15 @@
</para></listitem>
<listitem><para>
- <literal>--skip-delay-key-write</literal>
- </para>
-
- <para>
- Ignore the <literal>DELAY_KEY_WRITE</literal> option for all
- tables. As of MySQL 4.0.3, you should use
- <literal>--delay-key-write=OFF</literal> instead. See
- <xref linkend="server-parameters"/>.
- </para></listitem>
-
- <listitem><para>
<literal>--skip-external-locking</literal>
</para>
<para>
- Don't use system locking. To use <command>isamchk</command> or
- <command>myisamchk</command>, you must shut down the server. See
- <xref linkend="stability"/>. In MySQL 3.23, you can use
- <literal>CHECK TABLE</literal> and <literal>REPAIR TABLE</literal>
- to check and repair <literal>MyISAM</literal> tables. This option
- previously was named <literal>--skip-locking</literal>.
+ Don't use system locking. To use <command>myisamchk</command>, you
+ must shut down the server. (See <xref linkend="stability"/>.) To
+ avoid this requirement, use <literal>CHECK TABLE</literal> and
+ <literal>REPAIR TABLE</literal> from the MySQL Monitor to check and
+ repair <literal>MyISAM</literal> tables.
</para></listitem>
<listitem><para>
@@ -3327,12 +3230,13 @@
<para>
This option causes the server not to use the privilege system at
- all. This gives everyone <emphasis>full access</emphasis> to all
- databases! (You can tell a running server to start using the grant
- tables again by executing a <command>mysqladmin
+ all. This gives anyone with access to the server
+ <emphasis>unrestricted access</emphasis> to <emphasis>all
+ databases</emphasis>. You can cause a running server to start using
+ the grant tables again by executing <command>mysqladmin
flush-privileges</command> or <command>mysqladmin reload</command>
- command, or by issuing a <literal>FLUSH PRIVILEGES</literal>
- statement.)
+ command from a system shell, or by issuing a MySQL <literal>FLUSH
+ PRIVILEGES</literal> statement.
</para></listitem>
<listitem><para>
@@ -3356,17 +3260,6 @@
</para></listitem>
<listitem><para>
- <literal>--skip-isam</literal>
- </para>
-
- <para>
- Disable the <literal>ISAM</literal> storage engine. As of MySQL
- 4.1, <literal>ISAM</literal> is disabled by default, so this option
- applies only if the server was configured with support for
- <literal>ISAM</literal>. This option was added in MySQL 4.1.1.
- </para></listitem>
-
- <listitem><para>
<literal>--skip-name-resolve</literal>
</para>
@@ -3385,8 +3278,10 @@
Disable the <literal>NDB Cluster</literal> storage engine. This is
the default for binaries that were built with <literal>NDB
Cluster</literal> storage engine support, this means that the
- system only allocates memory and other resources for this storage
- engine if it is explicitly enabled.
+ system allocates memory and other resources for this storage engine
+ only if <literal>--skip-ndbcluster</literal> is explicitly
+ overridden using the <literal>--ndbcluster</literal> option. See
+ <xref linkend="mysql-cluster-quick"/> for an example of usage.
</para></listitem>
<listitem><para>
@@ -3402,29 +3297,12 @@
</para></listitem>
<listitem><para>
- <literal>--skip-new</literal>
- </para>
-
- <para>
- Don't use new, possibly wrong routines.
- </para></listitem>
-
- <listitem><para>
- <literal>--skip-symlink</literal>
- </para>
-
- <para>
- This is the old form of <literal>--skip-symbolic-links</literal>,
- for use before MySQL 4.0.13.
- </para></listitem>
-
- <listitem><para>
<literal>--standalone</literal>
</para>
<para>
- Windows-NT based systems only, instructs MySQL server to not run as
- a service.
+ Windows-NT based systems only; instructs the MySQL server not to
+ run as a service.
</para></listitem>
<listitem><para>
@@ -3458,10 +3336,7 @@
</itemizedlist>
</para>
-
- <para>
- This option was added in MySQL 4.0.13.
- </para></listitem>
+ </listitem>
<listitem><para>
<literal>--skip-safemalloc</literal>
@@ -3510,17 +3385,12 @@
<listitem><para>
<literal>--socket=<replaceable>path</replaceable></literal>
-
-<!-- Put the Unix description first, because the option name relates directly -->
- </para>
-
- <para>
-<!-- to the Unix meaning. Putting the Windows meaning first makes this more -->
- </para>
-
- <para>
-<!-- confusing. -->
</para>
+<!--
+ Put the Unix description first, because the option name relates directly
+ to the Unix meaning. Putting the Windows meaning first makes this more
+ confusing.
+-->
<para>
On Unix, this option specifies the Unix socket file to use for
@@ -3529,14 +3399,11 @@
specifies the pipe name to use for local connections that use a
named pipe. The default value is <literal>MySQL</literal>.
</para>
-
- <para>
-<!-- TODO: some of these option values currently are unimplemented. -->
- </para>
-
- <para>
-<!-- Need to say which ones. -->
- </para></listitem>
+ </listitem>
+<!--
+ TODO: some of these option values currently are unimplemented.
+ Need to say which ones.
+-->
<listitem><para>
<literal>--sql-mode=<replaceable>value</replaceable>[,<replaceable>value</replaceable>[,<replaceable>value</replaceable>...]]</literal>
@@ -3544,7 +3411,6 @@
<para>
Set the SQL mode for MySQL. See <xref linkend="server-sql-mode"/>.
- This option was added in 3.23.41.
</para></listitem>
<listitem><para>
@@ -3583,12 +3449,12 @@
The path of the directory to use for creating temporary files. It
might be useful if your default <literal>/tmp</literal> directory
resides on a partition that is too small to hold temporary tables.
- Starting from MySQL 4.1, this option accepts several paths that are
- used in round-robin fashion. Paths should be separated by colon
- characters ('<literal>:</literal>') on Unix and semicolon
- characters ('<literal>;</literal>') on Windows, NetWare, and OS/2.
- If the MySQL server is acting as a replication slave, you should
- not set <literal>--tmpdir</literal> to point to a directory on a
+ In MySQL 5.0, this option accepts several paths that are used in
+ round-robin fashion. Paths should be separated by colon characters
+ ('<literal>:</literal>') on Unix and semicolon characters
+ ('<literal>;</literal>') on Windows, NetWare, and OS/2. If the
+ MySQL server is acting as a replication slave, you should not set
+ <literal>--tmpdir</literal> to point to a directory on a
memory-based filesystem or to a directory that is cleared when the
server host restarts. A replication slave needs some of its
temporary files to survive a machine restart so that it can
@@ -3621,14 +3487,13 @@
</para>
<para>
- Starting from MySQL 3.23.56 and 4.0.12: To avoid a possible
- security hole where a user adds a <literal>--user=root</literal>
- option to some <filename>my.cnf</filename> file (thus causing the
- server to run as <literal>root</literal>),
- <command>mysqld</command> uses only the first
- <literal>--user</literal> option specified and produces a warning
- if there are multiple <literal>--user</literal> options. Options in
- <filename>/etc/my.cnf</filename> and
+ To avoid a possible security hole where a user adds a
+ <literal>--user=root</literal> option to a
+ <filename>my.cnf</filename> file (thus causing the server to run as
+ <literal>root</literal>), <command>mysqld</command> uses only the
+ first <literal>--user</literal> option specified and produces a
+ warning if there are multiple <literal>--user</literal> options.
+ Options in <filename>/etc/my.cnf</filename> and
<filename>$MYSQL_HOME/my.cnf</filename> are processed before
command-line options, so it is recommended that you put a
<literal>--user</literal> option in
@@ -3652,7 +3517,7 @@
</itemizedlist>
<para>
- As of MySQL 4.0, you can assign a value to a server system variable
+ In MySQL 5.0, you can assign a value to a server system variable
by using an option of the form
<literal>--<replaceable>var_name</replaceable>=<replaceable>value</replaceable></literal>.
For example, <literal>--key_buffer_size=32M</literal> sets the
@@ -3666,12 +3531,14 @@
allowed.
</para>
+<!-- TODO: Determine if this is still supported at all in MySQL 5.0. -->
+
<para>
It is also possible to set variables by using
<literal>--set-variable=<replaceable>var_name</replaceable>=<replaceable>value</replaceable></literal>
or <literal>-O
<replaceable>var_name</replaceable>=<replaceable>value</replaceable></literal>
- syntax. However, this syntax is deprecated as of MySQL 4.0.
+ syntax. However, this syntax is now deprecated.
</para>
<para>
@@ -3701,10 +3568,10 @@
<title id='title-server-sql-mode'>&title-server-sql-mode;</title>
<para>
- The MySQL server can operate in different SQL modes, and (as of
- MySQL 4.1) can apply these modes differentially for different
- clients. This allows an application to tailor server operation to
- its own requirements.
+ The MySQL server can operate in different SQL modes, and can apply
+ these modes differently for different clients. This allows each
+ application to tailor the server's operating mode to its own
+ requirements.
</para>
<para>
@@ -3723,15 +3590,15 @@
</para>
<para>
- Beginning with MySQL 4.1, you can also change the SQL mode after
- startup time by setting the <literal>sql_mode</literal> variable
- with a <literal>SET [SESSION|GLOBAL]
- sql_mode='<replaceable>modes</replaceable>'</literal> statement.
- Setting the <literal>GLOBAL</literal> variable requires the
- <literal>SUPER</literal> privilege and affects the operation of all
- clients that connect from that time on. Setting the
+ In MySQL 5.0, you can also change the SQL mode after startup time by
+ setting the <literal>sql_mode</literal> variable using a
+ <literal>SET [SESSION|GLOBAL] sql_mode='<replaceable>modes</replaceable>'</literal>
+ statement. Setting the <literal>GLOBAL</literal> variable requires
+ the <literal>SUPER</literal> privilege and affects the operation of
+ all clients that connect from that time on. Setting the
<literal>SESSION</literal> variable affects only the current client.
- Any client can change its session <literal>sql_mode</literal> value.
+ Any client can change its own session <literal>sql_mode</literal>
+ value at any time.
</para>
<para>
@@ -3759,7 +3626,6 @@
<para>
Change syntax and behavior to be more conformant to standard SQL.
- (New in MySQL 4.1.1)
</para>
<para>
@@ -3777,7 +3643,7 @@
table, abort the statement. For a non-transactional table, abort
the statement if the value occurs in a single-row statement or the
first row of a multiple-row statement. More detail is given later
- in this section. (New in MySQL 5.0.2)
+ in this section. (Implemented in MySQL 5.0.2)
</para>
<para>
@@ -3799,7 +3665,7 @@
as the error is noticed. This may not be what you want if you are
using a non-transactional storage engine, because data changes made
prior to the error are not be rolled back, resulting in a
- ``partially done'' update. (New in MySQL 5.0.2)
+ ``partially done'' update. (Added in MySQL 5.0.2)
</para></listitem>
</itemizedlist>
@@ -3815,7 +3681,7 @@
</para>
<para>
- The following list describes all the supported modes:
+ The following list describes all supported modes:
</para>
<itemizedlist>
@@ -3841,13 +3707,14 @@
</para>
<para>
- This mode is new in MySQL 5.0.2. Before 5.0.2, this was the default
- MySQL date-handling mode. As of 5.0.2, enabling strict mode causes
- the server to require that month and day values be legal, not just
- in the range from 1 to 12 and 1 to 31. For example,
- <literal>'2004-04-31'</literal> is legal with strict mode disabled,
- but illegal with strict mode enabled. To allow such dates in strict
- mode, enable <literal>ALLOW_INVALID_DATES</literal> as well.
+ This mode is implemented in MySQL 5.0.2. Before 5.0.2, this was the
+ default MySQL date-handling mode. As of 5.0.2, enabling strict mode
+ causes the server to require that month and day values be legal,
+ and not merely in the range 1 to 12 and 1 to 31, respectively. For
+ example, <literal>'2004-04-31'</literal> is legal with strict mode
+ disabled, but illegal with strict mode enabled. To allow such dates
+ in strict mode, enable <literal>ALLOW_INVALID_DATES</literal> as
+ well.
</para>
<para>
@@ -3866,7 +3733,7 @@
quote character. You can still use '<literal>`</literal>' to quote
identifiers in ANSI mode. With <literal>ANSI_QUOTES</literal>
enabled, you cannot use double quotes to quote a literal string,
- because it is interpreted as an identifier. (New in MySQL 4.0.0)
+ because it is interpreted as an identifier.
</para>
<para>
@@ -3889,8 +3756,8 @@
<literal>NULL</literal> for divisions by zero. If used in
<literal>INSERT IGNORE</literal> or <literal>UPDATE
IGNORE</literal>, MySQL generates a warning for divisions by zero,
- but the result of the operation is <literal>NULL</literal>. (New in
- MySQL 5.0.2)
+ but the result of the operation is <literal>NULL</literal>.
+ (Implmented in MySQL 5.0.2)
</para>
<para>
@@ -3910,7 +3777,7 @@
c)</literal>. Before MySQL 5.0.2, the expression is parsed as
<literal>(NOT a) BETWEEN b AND c</literal>. The old
higher-precedence behavior can be obtained by enabling the
- <literal>HIGH_NOT_PRECEDENCE</literal> SQL mode. (New in MySQL
+ <literal>HIGH_NOT_PRECEDENCE</literal> SQL mode. (Added in MySQL
5.0.2)
</para>
@@ -3953,10 +3820,6 @@
</para>
<para>
- (New in MySQL 4.0.0)
- </para>
-
- <para>
<indexterm type="concept">
<primary>NO_AUTO_CREATE_USER SQL mode</primary>
</indexterm>
@@ -3969,7 +3832,7 @@
<para>
Prevent <literal>GRANT</literal> from automatically creating new
users if it would otherwise do so, unless a password also is
- specified. (New in MySQL 5.0.2)
+ specified. (Added in MySQL 5.0.2)
</para>
<para>
@@ -3989,7 +3852,7 @@
<literal>NULL</literal> or <literal>0</literal> into it.
<literal>NO_AUTO_VALUE_ON_ZERO</literal> suppresses this behavior
for <literal>0</literal> so that only <literal>NULL</literal>
- generates the next sequence number. (New in MySQL 4.1.1)
+ generates the next sequence number.
</para>
<para>
@@ -4001,9 +3864,9 @@
<literal>0</literal> values, resulting in a table with different
contents than the one that was dumped. Enabling
<literal>NO_AUTO_VALUE_ON_ZERO</literal> before reloading the dump
- file solves this problem. As of MySQL 4.1.1,
- <command>mysqldump</command> automatically includes a statement in
- the dump output to enable <literal>NO_AUTO_VALUE_ON_ZERO</literal>.
+ file solves this problem. In MySQL 5.0,
+ <command>mysqldump</command> automatically includes in its output a
+ statement enabling <literal>NO_AUTO_VALUE_ON_ZERO</literal>.
</para>
<para>
@@ -4019,8 +3882,8 @@
<para>
Disable the use of the backslash character ('<literal>\</literal>')
as an escape character within strings. With this mode enabled,
- backslash becomes any ordinary character like any other. (New in
- MySQL 5.0.1)
+ backslash becomes any ordinary character like any other.
+ (Implemented in MySQL 5.0.1)
</para>
<para>
@@ -4037,7 +3900,6 @@
When creating a table, ignore all <literal>INDEX
DIRECTORY</literal> and <literal>DATA DIRECTORY</literal>
directives. This option is useful on slave replication servers.
- (New in MySQL 4.0.15)
</para>
</listitem>
@@ -4063,8 +3925,7 @@
<para>
Don't print MySQL-specific column options in the output of
<literal>SHOW CREATE TABLE</literal>. This mode is used by
- <command>mysqldump</command> in portability mode. (New in MySQL
- 4.1.1)
+ <command>mysqldump</command> in portability mode.
</para>
<para>
@@ -4080,8 +3941,7 @@
<para>
Don't print MySQL-specific index options in the output of
<literal>SHOW CREATE TABLE</literal>. This mode is used by
- <command>mysqldump</command> in portability mode. (New in MySQL
- 4.1.1)
+ <command>mysqldump</command> in portability mode.
</para>
<para>
@@ -4098,7 +3958,7 @@
Don't print MySQL-specific table options (such as
<literal>ENGINE</literal>) in the output of <literal>SHOW CREATE
TABLE</literal>. This mode is used by <command>mysqldump</command>
- in portability mode. (New in MySQL 4.1.1)
+ in portability mode.
</para>
<para>
@@ -4115,8 +3975,7 @@
In subtraction operations, don't mark the result as
<literal>UNSIGNED</literal> if one of the operands is unsigned.
Note that this makes <literal>UNSIGNED BIGINT</literal> not 100%
- usable in all contexts. See <xref linkend="cast-functions"/>. (New
- in MySQL 4.0.2)
+ usable in all contexts. See <xref linkend="cast-functions"/>.
</para>
<para>
@@ -4133,7 +3992,7 @@
In strict mode, don't allow <literal>'0000-00-00'</literal> as a
valid date. You can still insert zero dates with the
<literal>IGNORE</literal> option. When not in strict mode, the date
- is accepted but a warning is generated. (New in MySQL 5.0.2)
+ is accepted but a warning is generated. (Added in MySQL 5.0.2)
</para>
<para>
@@ -4150,8 +4009,8 @@
In strict mode, don't accept dates where the month or day part is
0. If used with the <literal>IGNORE</literal> option, we insert a
<literal>'0000-00-00'</literal> date for any such date. When not in
- strict mode, the date is accepted but a warning is generated. (New
- in MySQL 5.0.2)
+ strict mode, the date is accepted but a warning is generated.
+ (Added in MySQL 5.0.2)
</para>
<para>
@@ -4165,8 +4024,8 @@
</para>
<para>
- Don't allow queries that in the <literal>GROUP BY</literal> part
- refer to a not selected column. (New in MySQL 4.0.0)
+ Do not allow queries that in the <literal>GROUP BY</literal> part
+ refer to a column that is not selected.
</para>
<para>
@@ -4182,7 +4041,7 @@
<para>
Treat <literal>||</literal> as a string concatenation operator
(same as <literal>CONCAT()</literal>) rather than as a synonym for
- <literal>OR</literal>. (New in MySQL 4.0.0)
+ <literal>OR</literal>.
</para>
<para>
@@ -4198,7 +4057,7 @@
<para>
Treat <literal>REAL</literal> as a synonym for
<literal>FLOAT</literal> rather than as a synonym for
- <literal>DOUBLE</literal>. (New in MySQL 4.0.0)
+ <literal>DOUBLE</literal>.
</para>
<para>
@@ -4213,7 +4072,7 @@
<para>
Enable strict mode for all storage engines. Invalid data values are
- rejected. Additional detail follows. (New in MySQL 5.0.2)
+ rejected. Additional detail follows. (Added in MySQL 5.0.2)
</para>
<para>
@@ -4228,8 +4087,8 @@
<para>
Enable strict mode for transactional storage engines, and when
- possible for non-transactional storage engines. Additional detail
- follows. (New in MySQL 5.0.2)
+ possible for non-transactional storage engines. Additional details
+ follow. (Implemented in MySQL 5.0.2)
</para></listitem>
</itemizedlist>
@@ -4306,8 +4165,9 @@
<para>
The following special modes are provided as shorthand for
combinations of mode values from the preceding list. All are
- available as of MySQL 4.1.1, except <literal>TRADITIONAL</literal>
- (5.0.2).
+ available in MySQL 5.0 beginning with version 5.0.0, except for
+ <literal>TRADITIONAL</literal>, which was implemented in MySQL
+ 5.0.2.
</para>
<para>
@@ -4330,7 +4190,7 @@
<para>
Equivalent to <literal>REAL_AS_FLOAT</literal>,
<literal>PIPES_AS_CONCAT</literal>, <literal>ANSI_QUOTES</literal>,
- <literal>IGNORE_SPACE</literal>. Before MySQL 4.1.11 and 5.0.3,
+ <literal>IGNORE_SPACE</literal>. Before MySQL 5.0.3,
<literal>ANSI</literal> also includes
<literal>ONLY_FULL_GROUP_BY</literal>. See
<xref linkend="ansi-mode"/>.
@@ -4479,9 +4339,12 @@
</itemizedlist>
-<!-- TODO: not a great node name; there is also a System Variables node. -->
-
</section>
+
+<!--
+ TODO: not a great node name; there is also a System Variables
+ node.
+-->
<section id="server-system-variables">
--- 1.7/refman-5.0/ndbcluster.xml 2005-06-30 12:37:34 +10:00
+++ 1.8/refman-5.0/ndbcluster.xml 2005-07-02 04:58:39 +10:00
@@ -5137,9 +5137,9 @@
</para>
<para>
- Disables the NDB Cluster storage engine. This is disabled by
- default for binaries where it is included; the option only applies
- if the server was configured to use the NDB Cluster storage
+ Disables the NDB Cluster storage engine. This option is activated
+ by default for binaries where it is included; the option only
+ applies if the server was configured to use the NDB Cluster storage
engine.
</para></listitem>
| Thread |
|---|
| • bk commit - mysqldoc@docsrva tree (jon:1.2924) | jon | 1 Jul |
