Author: paul
Date: 2006-01-28 20:13:56 +0100 (Sat, 28 Jan 2006)
New Revision: 1082
Log:
r6810@frost: paul | 2006-01-28 13:11:47 -0600
General revisions.
Modified:
trunk/
trunk/refman-4.1/sql-syntax.xml
trunk/refman-5.0/sql-syntax.xml
trunk/refman-5.1/sql-syntax.xml
Property changes on: trunk
___________________________________________________________________
Name: svk:merge
- b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:6809
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:2588
+ b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:6810
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:2588
Modified: trunk/refman-4.1/sql-syntax.xml
===================================================================
--- trunk/refman-4.1/sql-syntax.xml 2006-01-28 19:13:38 UTC (rev 1081)
+++ trunk/refman-4.1/sql-syntax.xml 2006-01-28 19:13:56 UTC (rev 1082)
@@ -2268,10 +2268,10 @@
</para>
<para>
- Set this to <literal>1</literal> if you want to delay key
- updates for the table until the table is closed. See the
- description of the <literal>delay_key_write</literal> system
- variable in <xref linkend="server-system-variables"/>.
+ Set this to 1 if you want to delay key updates for the table
+ until the table is closed. See the description of the
+ <literal>delay_key_write</literal> system variable in
+ <xref linkend="server-system-variables"/>.
(<literal>MyISAM</literal> only.)
</para>
</listitem>
@@ -12717,17 +12717,15 @@
</para>
<para>
- Set the autocommit mode. If set to <literal>1</literal>, all
- changes to a table take effect immediately. If set to
- <literal>0</literal>, you have to use
+ Set the autocommit mode. If set to 1, all changes to a table
+ take effect immediately. If set to 0 you have to use
<literal>COMMIT</literal> to accept a transaction or
<literal>ROLLBACK</literal> to cancel it. By default, client
connections begin with <literal>AUTOCOMMENT</literal> set to
- 1. If you change <literal>AUTOCOMMIT</literal> mode from
- <literal>0</literal> to <literal>1</literal>, MySQL performs
- an automatic <literal>COMMIT</literal> of any open
- transaction. Another way to begin a transaction is to use a
- <literal>START TRANSACTION</literal> or
+ 1. If you change <literal>AUTOCOMMIT</literal> mode from 0
+ to 1, MySQL performs an automatic <literal>COMMIT</literal>
+ of any open transaction. Another way to begin a transaction
+ is to use a <literal>START TRANSACTION</literal> or
<literal>BEGIN</literal> statement. See
<xref linkend="commit"/>.
</para>
@@ -12743,13 +12741,12 @@
</para>
<para>
- If set to <literal>1</literal>, all temporary tables are
- stored on disk rather than in memory. This is a little
- slower, but the error <literal>The table
- <replaceable>tbl_name</replaceable> is full</literal> does
- not occur for <literal>SELECT</literal> operations that
- require a large temporary table. The default value for a new
- connection is <literal>0</literal> (use in-memory temporary
+ If set to 1, all temporary tables are stored on disk rather
+ than in memory. This is a little slower, but the error
+ <literal>The table <replaceable>tbl_name</replaceable> is
+ full</literal> does not occur for <literal>SELECT</literal>
+ operations that require a large temporary table. The default
+ value for a new connection is 0 (use in-memory temporary
tables). As of MySQL 4.0, you should normally never need to
set this variable, because MySQL automatically converts
in-memory tables to disk-based tables as necessary.
@@ -12803,13 +12800,12 @@
</para>
<para>
- If set to <literal>1</literal> (the default), foreign key
- constraints for <literal>InnoDB</literal> tables are
- checked. If set to <literal>0</literal>, they are ignored.
- Disabling foreign key checking can be useful for reloading
- <literal>InnoDB</literal> tables in an order different than
- that required by their parent/child relationships. This
- variable was added in MySQL 3.23.52. See
+ If set to 1 (the default), foreign key constraints for
+ <literal>InnoDB</literal> tables are checked. If set to 0,
+ they are ignored. Disabling foreign key checking can be
+ useful for reloading <literal>InnoDB</literal> tables in an
+ order different than that required by their parent/child
+ relationships. This variable was added in MySQL 3.23.52. See
<xref linkend="innodb-foreign-key-constraints"/>.
</para>
</listitem>
@@ -12963,8 +12959,8 @@
</para>
<para>
- If set to <literal>1</literal> (the default), you can find
- the last inserted row for a table that contains an
+ If set to 1 (the default), you can find the last inserted
+ row for a table that contains an
<literal>AUTO_INCREMENT</literal> column by using the
following construct:
</para>
@@ -12984,22 +12980,20 @@
</para>
<para>
- If set to <literal>0</literal>, MySQL aborts
- <literal>SELECT</literal> statements that are likely to take
- a very long time to execute (that is, statements for which
- the optimizer estimates that the number of examined rows
- exceeds the value of <literal>max_join_size</literal>). This
- is useful when an inadvisable <literal>WHERE</literal>
- statement has been issued. The default value for a new
- connection is <literal>1</literal>, which allows all
- <literal>SELECT</literal> statements.
+ If set to 0, MySQL aborts <literal>SELECT</literal>
+ statements that are likely to take a very long time to
+ execute (that is, statements for which the optimizer
+ estimates that the number of examined rows exceeds the value
+ of <literal>max_join_size</literal>). This is useful when an
+ inadvisable <literal>WHERE</literal> statement has been
+ issued. The default value for a new connection is 1, which
+ allows all <literal>SELECT</literal> statements.
</para>
<para>
If you set the <literal>max_join_size</literal> system
variable to a value other than <literal>DEFAULT</literal>,
- <literal>SQL_BIG_SELECTS</literal> is set to
- <literal>0</literal>.
+ <literal>SQL_BIG_SELECTS</literal> is set to 0.
</para>
</listitem>
@@ -13024,10 +13018,10 @@
</para>
<para>
- If set to <literal>0</literal>, no logging is done to the
- binary log for the client. The client must have the
- <literal>SUPER</literal> privilege to set this option. This
- variable was added in MySQL 3.23.16.
+ If set to 0, no logging is done to the binary log for the
+ client. The client must have the <literal>SUPER</literal>
+ privilege to set this option. This variable was added in
+ MySQL 3.23.16.
</para>
</listitem>
@@ -13037,8 +13031,8 @@
</para>
<para>
- If set to <literal>1</literal>, no logging is done to the
- general query log for this client. The client must have the
+ If set to 1, no logging is done to the general query log for
+ this client. The client must have the
<literal>SUPER</literal> privilege to set this option.
</para>
</listitem>
@@ -13062,14 +13056,14 @@
</para>
<para>
- When set to <literal>1</literal> (the default), warnings of
- <literal>Note</literal> level are recorded. When set to
- <literal>0</literal>, <literal>Note</literal> warnings are
- suppressed. <command>mysqldump</command> includes output to
- set this variable to <literal>0</literal> so that reloading
- the dump file does not produce warnings for events that do
- not affect the integrity of the reload operation.
- <literal>SQL_NOTES</literal> was added in MySQL 4.1.11.
+ When set to 1 (the default), warnings of
+ <literal>Note</literal> level are recorded. When set to 0,
+ <literal>Note</literal> warnings are suppressed.
+ <command>mysqldump</command> includes output to set this
+ variable to 0 so that reloading the dump file does not
+ produce warnings for events that do not affect the integrity
+ of the reload operation. <literal>SQL_NOTES</literal> was
+ added in MySQL 4.1.11.
</para>
</listitem>
@@ -13079,12 +13073,11 @@
</para>
<para>
- If set to <literal>1</literal>, the server quotes
- identifiers for <literal>SHOW CREATE TABLE</literal> and
- <literal>SHOW CREATE DATABASE</literal> statements. If set
- to <literal>0</literal>, quoting is disabled. This option is
- enabled by default so that replication works for identifiers
- that require quoting. See
+ If set to 1, the server quotes identifiers for <literal>SHOW
+ CREATE TABLE</literal> and <literal>SHOW CREATE
+ DATABASE</literal> statements. If set to 0, quoting is
+ disabled. This option is enabled by default so that
+ replication works for identifiers that require quoting. See
<xref linkend="show-create-table"/>, and
<xref linkend="show-create-database"/>. This variable was
added in MySQL 3.23.26.
@@ -13097,10 +13090,9 @@
</para>
<para>
- If set to <literal>1</literal>, MySQL aborts
- <literal>UPDATE</literal> or <literal>DELETE</literal>
- statements that do not use a key in the
- <literal>WHERE</literal> clause or a
+ If set to 1, MySQL aborts <literal>UPDATE</literal> or
+ <literal>DELETE</literal> statements that do not use a key
+ in the <literal>WHERE</literal> clause or a
<literal>LIMIT</literal> clause. This makes it possible to
catch <literal>UPDATE</literal> or <literal>DELETE</literal>
statements where keys are not used properly and that would
@@ -13178,15 +13170,14 @@
</para>
<para>
- If set to <literal>1</literal> (the default), uniqueness
- checks for secondary indexes in <literal>InnoDB</literal>
- tables are performed. If set to <literal>0</literal>,
- uniqueness checks are not done for index entries inserted
- into <literal>InnoDB</literal>'s insert buffer. If you know
- for certain that your data does not contain uniqueness
- violations, you can set this to 0 to speed up large table
- imports to <literal>InnoDB</literal>. This variable was
- added in MySQL 3.23.52.
+ If set to 1 (the default), uniqueness checks for secondary
+ indexes in <literal>InnoDB</literal> tables are performed.
+ If set to 0, uniqueness checks are not done for index
+ entries inserted into <literal>InnoDB</literal>'s insert
+ buffer. If you know for certain that your data does not
+ contain uniqueness violations, you can set this to 0 to
+ speed up large table imports to <literal>InnoDB</literal>.
+ This variable was added in MySQL 3.23.52.
</para>
</listitem>
@@ -15924,8 +15915,7 @@
<literal>max_error_count</literal>. In the following example,
the <literal>ALTER TABLE</literal> statement produces three
warning messages, but only one is stored because
- <literal>max_error_count</literal> has been set to
- <literal>1</literal>:
+ <literal>max_error_count</literal> has been set to 1:
</para>
<programlisting>
@@ -15963,16 +15953,15 @@
<para>
To disable warnings, set <literal>max_error_count</literal> to
- <literal>0</literal>. In this case,
- <literal>warning_count</literal> still indicates how many
- warnings have occurred, but none of the messages are stored.
+ 0. In this case, <literal>warning_count</literal> still
+ indicates how many warnings have occurred, but none of the
+ messages are stored.
</para>
<para>
As of MySQL 4.1.11, you can set the
- <literal>SQL_NOTES</literal> session variable to
- <literal>0</literal> to cause <literal>Note</literal>-level
- warnings not to be recorded.
+ <literal>SQL_NOTES</literal> session variable to 0 to cause
+ <literal>Note</literal>-level warnings not to be recorded.
</para>
</section>
@@ -17224,8 +17213,9 @@
log files</emphasis> and starts a new one, unless you specify
<literal>RELAY_LOG_FILE</literal> or
<literal>RELAY_LOG_POS</literal>. In that case, relay logs are
- kept; as of MySQL 4.1.1 the <literal>relay_log_purge</literal>
- global variable is set silently to 0.
+ kept; as of MySQL 4.1.1, the
+ <literal>relay_log_purge</literal> global variable is set
+ silently to 0.
</para>
<para>
Modified: trunk/refman-5.0/sql-syntax.xml
===================================================================
--- trunk/refman-5.0/sql-syntax.xml 2006-01-28 19:13:38 UTC (rev 1081)
+++ trunk/refman-5.0/sql-syntax.xml 2006-01-28 19:13:56 UTC (rev 1082)
@@ -2301,10 +2301,10 @@
</para>
<para>
- Set this to <literal>1</literal> if you want to delay key
- updates for the table until the table is closed. See the
- description of the <literal>delay_key_write</literal> system
- variable in <xref linkend="server-system-variables"/>.
+ Set this to 1 if you want to delay key updates for the table
+ until the table is closed. See the description of the
+ <literal>delay_key_write</literal> system variable in
+ <xref linkend="server-system-variables"/>.
(<literal>MyISAM</literal> only.)
</para>
</listitem>
@@ -13881,17 +13881,15 @@
</para>
<para>
- Set the autocommit mode. If set to <literal>1</literal>, all
- changes to a table take effect immediately. If set to
- <literal>0</literal>, you have to use
+ Set the autocommit mode. If set to 1, all changes to a table
+ take effect immediately. If set to 0 you have to use
<literal>COMMIT</literal> to accept a transaction or
<literal>ROLLBACK</literal> to cancel it. By default, client
connections begin with <literal>AUTOCOMMENT</literal> set to
- 1. If you change <literal>AUTOCOMMIT</literal> mode from
- <literal>0</literal> to <literal>1</literal>, MySQL performs
- an automatic <literal>COMMIT</literal> of any open
- transaction. Another way to begin a transaction is to use a
- <literal>START TRANSACTION</literal> or
+ 1. If you change <literal>AUTOCOMMIT</literal> mode from 0
+ to 1, MySQL performs an automatic <literal>COMMIT</literal>
+ of any open transaction. Another way to begin a transaction
+ is to use a <literal>START TRANSACTION</literal> or
<literal>BEGIN</literal> statement. See
<xref linkend="commit"/>.
</para>
@@ -13907,13 +13905,12 @@
</para>
<para>
- If set to <literal>1</literal>, all temporary tables are
- stored on disk rather than in memory. This is a little
- slower, but the error <literal>The table
- <replaceable>tbl_name</replaceable> is full</literal> does
- not occur for <literal>SELECT</literal> operations that
- require a large temporary table. The default value for a new
- connection is <literal>0</literal> (use in-memory temporary
+ If set to 1, all temporary tables are stored on disk rather
+ than in memory. This is a little slower, but the error
+ <literal>The table <replaceable>tbl_name</replaceable> is
+ full</literal> does not occur for <literal>SELECT</literal>
+ operations that require a large temporary table. The default
+ value for a new connection is 0 (use in-memory temporary
tables). Normally, you should never need to set this
variable, because in-memory tables are automatically
converted to disk-based tables as required.
@@ -14005,12 +14002,12 @@
</para>
<para>
- If set to <literal>1</literal> (the default), foreign key
- constraints for <literal>InnoDB</literal> tables are
- checked. If set to <literal>0</literal>, they are ignored.
- Disabling foreign key checking can be useful for reloading
- <literal>InnoDB</literal> tables in an order different than
- that required by their parent/child relationships. See
+ If set to 1 (the default), foreign key constraints for
+ <literal>InnoDB</literal> tables are checked. If set to 0,
+ they are ignored. Disabling foreign key checking can be
+ useful for reloading <literal>InnoDB</literal> tables in an
+ order different than that required by their parent/child
+ relationships. See
<xref linkend="innodb-foreign-key-constraints"/>.
</para>
</listitem>
@@ -14162,8 +14159,8 @@
</para>
<para>
- If set to <literal>1</literal> (the default), you can find
- the last inserted row for a table that contains an
+ If set to 1 (the default), you can find the last inserted
+ row for a table that contains an
<literal>AUTO_INCREMENT</literal> column by using the
following construct:
</para>
@@ -14183,22 +14180,20 @@
</para>
<para>
- If set to <literal>0</literal>, MySQL aborts
- <literal>SELECT</literal> statements that are likely to take
- a very long time to execute (that is, statements for which
- the optimizer estimates that the number of examined rows
- exceeds the value of <literal>max_join_size</literal>). This
- is useful when an inadvisable <literal>WHERE</literal>
- statement has been issued. The default value for a new
- connection is <literal>1</literal>, which allows all
- <literal>SELECT</literal> statements.
+ If set to 0, MySQL aborts <literal>SELECT</literal>
+ statements that are likely to take a very long time to
+ execute (that is, statements for which the optimizer
+ estimates that the number of examined rows exceeds the value
+ of <literal>max_join_size</literal>). This is useful when an
+ inadvisable <literal>WHERE</literal> statement has been
+ issued. The default value for a new connection is 1, which
+ allows all <literal>SELECT</literal> statements.
</para>
<para>
If you set the <literal>max_join_size</literal> system
variable to a value other than <literal>DEFAULT</literal>,
- <literal>SQL_BIG_SELECTS</literal> is set to
- <literal>0</literal>.
+ <literal>SQL_BIG_SELECTS</literal> is set to 0.
</para>
</listitem>
@@ -14222,9 +14217,9 @@
</para>
<para>
- If set to <literal>0</literal>, no logging is done to the
- binary log for the client. The client must have the
- <literal>SUPER</literal> privilege to set this option.
+ If set to 0, no logging is done to the binary log for the
+ client. The client must have the <literal>SUPER</literal>
+ privilege to set this option.
</para>
</listitem>
@@ -14234,8 +14229,8 @@
</para>
<para>
- If set to <literal>1</literal>, no logging is done to the
- general query log for this client. The client must have the
+ If set to 1, no logging is done to the general query log for
+ this client. The client must have the
<literal>SUPER</literal> privilege to set this option.
</para>
</listitem>
@@ -14257,14 +14252,14 @@
</para>
<para>
- When set to <literal>1</literal> (the default), warnings of
- <literal>Note</literal> level are recorded. When set to
- <literal>0</literal>, <literal>Note</literal> warnings are
- suppressed. <command>mysqldump</command> includes output to
- set this variable to <literal>0</literal> so that reloading
- the dump file does not produce warnings for events that do
- not affect the integrity of the reload operation.
- <literal>SQL_NOTES</literal> was added in MySQL 5.0.3.
+ When set to 1 (the default), warnings of
+ <literal>Note</literal> level are recorded. When set to 0,
+ <literal>Note</literal> warnings are suppressed.
+ <command>mysqldump</command> includes output to set this
+ variable to 0 so that reloading the dump file does not
+ produce warnings for events that do not affect the integrity
+ of the reload operation. <literal>SQL_NOTES</literal> was
+ added in MySQL 5.0.3.
</para>
</listitem>
@@ -14274,12 +14269,11 @@
</para>
<para>
- If set to <literal>1</literal>, the server quotes
- identifiers for <literal>SHOW CREATE TABLE</literal> and
- <literal>SHOW CREATE DATABASE</literal> statements. If set
- to <literal>0</literal>, quoting is disabled. This option is
- enabled by default so that replication works for identifiers
- that require quoting. See
+ If set to 1, the server quotes identifiers for <literal>SHOW
+ CREATE TABLE</literal> and <literal>SHOW CREATE
+ DATABASE</literal> statements. If set to 0, quoting is
+ disabled. This option is enabled by default so that
+ replication works for identifiers that require quoting. See
<xref linkend="show-create-table"/>, and
<xref linkend="show-create-database"/>.
</para>
@@ -14291,10 +14285,9 @@
</para>
<para>
- If set to <literal>1</literal>, MySQL aborts
- <literal>UPDATE</literal> or <literal>DELETE</literal>
- statements that do not use a key in the
- <literal>WHERE</literal> clause or a
+ If set to 1, MySQL aborts <literal>UPDATE</literal> or
+ <literal>DELETE</literal> statements that do not use a key
+ in the <literal>WHERE</literal> clause or a
<literal>LIMIT</literal> clause. This makes it possible to
catch <literal>UPDATE</literal> or <literal>DELETE</literal>
statements where keys are not used properly and that would
@@ -14390,14 +14383,13 @@
</para>
<para>
- If set to <literal>1</literal> (the default), uniqueness
- checks for secondary indexes in <literal>InnoDB</literal>
- tables are performed. If set to <literal>0</literal>,
- uniqueness checks are not done for index entries inserted
- into <literal>InnoDB</literal>'s insert buffer. If you know
- for certain that your data does not contain uniqueness
- violations, you can set this to 0 to speed up large table
- imports to <literal>InnoDB</literal>.
+ If set to 1 (the default), uniqueness checks for secondary
+ indexes in <literal>InnoDB</literal> tables are performed.
+ If set to 0, uniqueness checks are not done for index
+ entries inserted into <literal>InnoDB</literal>'s insert
+ buffer. If you know for certain that your data does not
+ contain uniqueness violations, you can set this to 0 to
+ speed up large table imports to <literal>InnoDB</literal>.
</para>
</listitem>
@@ -17492,8 +17484,7 @@
<literal>max_error_count</literal>. In the following example,
the <literal>ALTER TABLE</literal> statement produces three
warning messages, but only one is stored because
- <literal>max_error_count</literal> has been set to
- <literal>1</literal>:
+ <literal>max_error_count</literal> has been set to 1:
</para>
<programlisting>
@@ -17531,16 +17522,15 @@
<para>
To disable warnings, set <literal>max_error_count</literal> to
- <literal>0</literal>. In this case,
- <literal>warning_count</literal> still indicates how many
- warnings have occurred, but none of the messages are stored.
+ 0. In this case, <literal>warning_count</literal> still
+ indicates how many warnings have occurred, but none of the
+ messages are stored.
</para>
<para>
As of MySQL 5.0.3, you can set the
- <literal>SQL_NOTES</literal> session variable to
- <literal>0</literal> to cause <literal>Note</literal>-level
- warnings not to be recorded.
+ <literal>SQL_NOTES</literal> session variable to 0 to cause
+ <literal>Note</literal>-level warnings not to be recorded.
</para>
</section>
@@ -18802,7 +18792,7 @@
<literal>RELAY_LOG_FILE</literal> or
<literal>RELAY_LOG_POS</literal>. In that case, relay logs are
kept; the <literal>relay_log_purge</literal> global variable
- is set silently to <literal>0</literal>.
+ is set silently to 0.
</para>
<para>
Modified: trunk/refman-5.1/sql-syntax.xml
===================================================================
--- trunk/refman-5.1/sql-syntax.xml 2006-01-28 19:13:38 UTC (rev 1081)
+++ trunk/refman-5.1/sql-syntax.xml 2006-01-28 19:13:56 UTC (rev 1082)
@@ -2561,10 +2561,10 @@
</para>
<para>
- Set this to <literal>1</literal> if you want to delay key
- updates for the table until the table is closed. See the
- description of the <literal>delay_key_write</literal> system
- variable in <xref linkend="server-system-variables"/>.
+ Set this to 1 if you want to delay key updates for the table
+ until the table is closed. See the description of the
+ <literal>delay_key_write</literal> system variable in
+ <xref linkend="server-system-variables"/>.
(<literal>MyISAM</literal> only.)
</para>
</listitem>
@@ -14360,17 +14360,15 @@
</para>
<para>
- Set the autocommit mode. If set to <literal>1</literal>, all
- changes to a table take effect immediately. If set to
- <literal>0</literal>, you have to use
+ Set the autocommit mode. If set to 1, all changes to a table
+ take effect immediately. If set to 0 you have to use
<literal>COMMIT</literal> to accept a transaction or
<literal>ROLLBACK</literal> to cancel it. By default, client
connections begin with <literal>AUTOCOMMENT</literal> set to
- 1. If you change <literal>AUTOCOMMIT</literal> mode from
- <literal>0</literal> to <literal>1</literal>, MySQL performs
- an automatic <literal>COMMIT</literal> of any open
- transaction. Another way to begin a transaction is to use a
- <literal>START TRANSACTION</literal> or
+ 1. If you change <literal>AUTOCOMMIT</literal> mode from 0
+ to 1, MySQL performs an automatic <literal>COMMIT</literal>
+ of any open transaction. Another way to begin a transaction
+ is to use a <literal>START TRANSACTION</literal> or
<literal>BEGIN</literal> statement. See
<xref linkend="commit"/>.
</para>
@@ -14386,13 +14384,12 @@
</para>
<para>
- If set to <literal>1</literal>, all temporary tables are
- stored on disk rather than in memory. This is a little
- slower, but the error <literal>The table
- <replaceable>tbl_name</replaceable> is full</literal> does
- not occur for <literal>SELECT</literal> operations that
- require a large temporary table. The default value for a new
- connection is <literal>0</literal> (use in-memory temporary
+ If set to 1, all temporary tables are stored on disk rather
+ than in memory. This is a little slower, but the error
+ <literal>The table <replaceable>tbl_name</replaceable> is
+ full</literal> does not occur for <literal>SELECT</literal>
+ operations that require a large temporary table. The default
+ value for a new connection is 0 (use in-memory temporary
tables). Normally, you should never need to set this
variable, because in-memory tables are automatically
converted to disk-based tables as required.
@@ -14484,12 +14481,12 @@
</para>
<para>
- If set to <literal>1</literal> (the default), foreign key
- constraints for <literal>InnoDB</literal> tables are
- checked. If set to <literal>0</literal>, they are ignored.
- Disabling foreign key checking can be useful for reloading
- <literal>InnoDB</literal> tables in an order different than
- that required by their parent/child relationships. See
+ If set to 1 (the default), foreign key constraints for
+ <literal>InnoDB</literal> tables are checked. If set to 0,
+ they are ignored. Disabling foreign key checking can be
+ useful for reloading <literal>InnoDB</literal> tables in an
+ order different than that required by their parent/child
+ relationships. See
<xref linkend="innodb-foreign-key-constraints"/>.
</para>
</listitem>
@@ -14640,8 +14637,8 @@
</para>
<para>
- If set to <literal>1</literal> (the default), you can find
- the last inserted row for a table that contains an
+ If set to 1 (the default), you can find the last inserted
+ row for a table that contains an
<literal>AUTO_INCREMENT</literal> column by using the
following construct:
</para>
@@ -14661,22 +14658,20 @@
</para>
<para>
- If set to <literal>0</literal>, MySQL aborts
- <literal>SELECT</literal> statements that are likely to take
- a very long time to execute (that is, statements for which
- the optimizer estimates that the number of examined rows
- exceeds the value of <literal>max_join_size</literal>). This
- is useful when an inadvisable <literal>WHERE</literal>
- statement has been issued. The default value for a new
- connection is <literal>1</literal>, which allows all
- <literal>SELECT</literal> statements.
+ If set to 0, MySQL aborts <literal>SELECT</literal>
+ statements that are likely to take a very long time to
+ execute (that is, statements for which the optimizer
+ estimates that the number of examined rows exceeds the value
+ of <literal>max_join_size</literal>). This is useful when an
+ inadvisable <literal>WHERE</literal> statement has been
+ issued. The default value for a new connection is 1, which
+ allows all <literal>SELECT</literal> statements.
</para>
<para>
If you set the <literal>max_join_size</literal> system
variable to a value other than <literal>DEFAULT</literal>,
- <literal>SQL_BIG_SELECTS</literal> is set to
- <literal>0</literal>.
+ <literal>SQL_BIG_SELECTS</literal> is set to 0.
</para>
</listitem>
@@ -14700,9 +14695,9 @@
</para>
<para>
- If set to <literal>0</literal>, no logging is done to the
- binary log for the client. The client must have the
- <literal>SUPER</literal> privilege to set this option.
+ If set to 0, no logging is done to the binary log for the
+ client. The client must have the <literal>SUPER</literal>
+ privilege to set this option.
</para>
</listitem>
@@ -14712,8 +14707,8 @@
</para>
<para>
- If set to <literal>1</literal>, no logging is done to the
- general query log for this client. The client must have the
+ If set to 1, no logging is done to the general query log for
+ this client. The client must have the
<literal>SUPER</literal> privilege to set this option.
</para>
</listitem>
@@ -14735,13 +14730,13 @@
</para>
<para>
- When set to <literal>1</literal> (the default), warnings of
- <literal>Note</literal> level are recorded. When set to
- <literal>0</literal>, <literal>Note</literal> warnings are
- suppressed. <command>mysqldump</command> includes output to
- set this variable to <literal>0</literal> so that reloading
- the dump file does not produce warnings for events that do
- not affect the integrity of the reload operation.
+ When set to 1 (the default), warnings of
+ <literal>Note</literal> level are recorded. When set to 0,
+ <literal>Note</literal> warnings are suppressed.
+ <command>mysqldump</command> includes output to set this
+ variable to 0 so that reloading the dump file does not
+ produce warnings for events that do not affect the integrity
+ of the reload operation.
</para>
</listitem>
@@ -14751,12 +14746,11 @@
</para>
<para>
- If set to <literal>1</literal>, the server quotes
- identifiers for <literal>SHOW CREATE TABLE</literal> and
- <literal>SHOW CREATE DATABASE</literal> statements. If set
- to <literal>0</literal>, quoting is disabled. This option is
- enabled by default so that replication works for identifiers
- that require quoting. See
+ If set to 1, the server quotes identifiers for <literal>SHOW
+ CREATE TABLE</literal> and <literal>SHOW CREATE
+ DATABASE</literal> statements. If set to 0, quoting is
+ disabled. This option is enabled by default so that
+ replication works for identifiers that require quoting. See
<xref linkend="show-create-table"/>, and
<xref linkend="show-create-database"/>.
</para>
@@ -14768,10 +14762,9 @@
</para>
<para>
- If set to <literal>1</literal>, MySQL aborts
- <literal>UPDATE</literal> or <literal>DELETE</literal>
- statements that do not use a key in the
- <literal>WHERE</literal> clause or a
+ If set to 1, MySQL aborts <literal>UPDATE</literal> or
+ <literal>DELETE</literal> statements that do not use a key
+ in the <literal>WHERE</literal> clause or a
<literal>LIMIT</literal> clause. This makes it possible to
catch <literal>UPDATE</literal> or <literal>DELETE</literal>
statements where keys are not used properly and that would
@@ -14867,14 +14860,13 @@
</para>
<para>
- If set to <literal>1</literal> (the default), uniqueness
- checks for secondary indexes in <literal>InnoDB</literal>
- tables are performed. If set to <literal>0</literal>,
- uniqueness checks are not done for index entries inserted
- into <literal>InnoDB</literal>'s insert buffer. If you know
- for certain that your data does not contain uniqueness
- violations, you can set this to 0 to speed up large table
- imports to <literal>InnoDB</literal>.
+ If set to 1 (the default), uniqueness checks for secondary
+ indexes in <literal>InnoDB</literal> tables are performed.
+ If set to 0, uniqueness checks are not done for index
+ entries inserted into <literal>InnoDB</literal>'s insert
+ buffer. If you know for certain that your data does not
+ contain uniqueness violations, you can set this to 0 to
+ speed up large table imports to <literal>InnoDB</literal>.
</para>
</listitem>
@@ -18011,8 +18003,7 @@
<literal>max_error_count</literal>. In the following example,
the <literal>ALTER TABLE</literal> statement produces three
warning messages, but only one is stored because
- <literal>max_error_count</literal> has been set to
- <literal>1</literal>:
+ <literal>max_error_count</literal> has been set to 1:
</para>
<programlisting>
@@ -18050,15 +18041,15 @@
<para>
To disable warnings, set <literal>max_error_count</literal> to
- <literal>0</literal>. In this case,
- <literal>warning_count</literal> still indicates how many
- warnings have occurred, but none of the messages are stored.
+ 0. In this case, <literal>warning_count</literal> still
+ indicates how many warnings have occurred, but none of the
+ messages are stored.
</para>
<para>
You can set the <literal>SQL_NOTES</literal> session variable
- to <literal>0</literal> to cause <literal>Note</literal>-level
- warnings not to be recorded.
+ to 0 to cause <literal>Note</literal>-level warnings not to be
+ recorded.
</para>
</section>
@@ -19317,7 +19308,7 @@
<literal>RELAY_LOG_FILE</literal> or
<literal>RELAY_LOG_POS</literal>. In that case, relay logs are
kept; the <literal>relay_log_purge</literal> global variable
- is set silently to <literal>0</literal>.
+ is set silently to 0.
</para>
<para>
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r1082 - in trunk: . refman-4.1 refman-5.0 refman-5.1 | paul | 28 Jan |
