Author: paul
Date: 2008-05-20 23:11:41 +0200 (Tue, 20 May 2008)
New Revision: 10792
Log:
r31568@frost: paul | 2008-05-20 16:06:40 -0500
Bug#24159; Effect of setting AUTO_INCREMENT for underlying MyISAM table
on inserts into MERGE table.
Modified:
trunk/it/refman-5.1/se-merge.xml
trunk/pt/refman-5.1/se-merge.xml
trunk/refman-4.1/storage-engines.xml
trunk/refman-5.0/se-merge.xml
trunk/refman-5.1/se-merge.xml
trunk/refman-6.0/se-merge.xml
Property changes on: trunk
___________________________________________________________________
Name: svk:merge
- 4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:35828
7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:31567
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:31325
+ 4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:35828
7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:31568
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:31325
Modified: trunk/it/refman-5.1/se-merge.xml
===================================================================
--- trunk/it/refman-5.1/se-merge.xml 2008-05-20 21:11:33 UTC (rev 10791)
+++ trunk/it/refman-5.1/se-merge.xml 2008-05-20 21:11:41 UTC (rev 10792)
Changed blocks: 1, Lines Added: 14, Lines Deleted: 0; 1118 bytes
@@ -619,6 +619,20 @@
<listitem>
<para>
+ The <literal>INSERT_METHOD</literal> table option for a
+ <literal>MERGE</literal> table indicates which underlying
+ <literal>MyISAM</literal> table to use for inserts into the
+ <literal>MERGE</literal> table. However, use of the
+ <literal>AUTO_INCREMENT</literal> table option for that
+ <literal>MyISAM</literal> table has no effect for inserts into
+ the <literal>MERGE</literal> table until at least one row has
+ been inserted directly into the <literal>MyISAM</literal>
+ table.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
In MySQL 5.1.15 and later, the definition of the
<literal>MyISAM</literal> tables and the
<literal>MERGE</literal> table are checked when the tables are
Modified: trunk/pt/refman-5.1/se-merge.xml
===================================================================
--- trunk/pt/refman-5.1/se-merge.xml 2008-05-20 21:11:33 UTC (rev 10791)
+++ trunk/pt/refman-5.1/se-merge.xml 2008-05-20 21:11:41 UTC (rev 10792)
Changed blocks: 1, Lines Added: 14, Lines Deleted: 0; 1118 bytes
@@ -619,6 +619,20 @@
<listitem>
<para>
+ The <literal>INSERT_METHOD</literal> table option for a
+ <literal>MERGE</literal> table indicates which underlying
+ <literal>MyISAM</literal> table to use for inserts into the
+ <literal>MERGE</literal> table. However, use of the
+ <literal>AUTO_INCREMENT</literal> table option for that
+ <literal>MyISAM</literal> table has no effect for inserts into
+ the <literal>MERGE</literal> table until at least one row has
+ been inserted directly into the <literal>MyISAM</literal>
+ table.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
In MySQL 5.1.15 and later, the definition of the
<literal>MyISAM</literal> tables and the
<literal>MERGE</literal> table are checked when the tables are
Modified: trunk/refman-4.1/storage-engines.xml
===================================================================
--- trunk/refman-4.1/storage-engines.xml 2008-05-20 21:11:33 UTC (rev 10791)
+++ trunk/refman-4.1/storage-engines.xml 2008-05-20 21:11:41 UTC (rev 10792)
Changed blocks: 1, Lines Added: 14, Lines Deleted: 0; 1170 bytes
@@ -2257,6 +2257,20 @@
<listitem>
<para>
+ The <literal>INSERT_METHOD</literal> table option for a
+ <literal>MERGE</literal> table indicates which underlying
+ <literal>MyISAM</literal> table to use for inserts into the
+ <literal>MERGE</literal> table. However, use of the
+ <literal>AUTO_INCREMENT</literal> table option for that
+ <literal>MyISAM</literal> table has no effect for inserts
+ into the <literal>MERGE</literal> table until at least one
+ row has been inserted directly into the
+ <literal>MyISAM</literal> table.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
Before MySQL 3.23.49, <literal>DELETE FROM
<replaceable>merge_table</replaceable></literal> used
without a <literal>WHERE</literal> clause only clears the
Modified: trunk/refman-5.0/se-merge.xml
===================================================================
--- trunk/refman-5.0/se-merge.xml 2008-05-20 21:11:33 UTC (rev 10791)
+++ trunk/refman-5.0/se-merge.xml 2008-05-20 21:11:41 UTC (rev 10792)
Changed blocks: 1, Lines Added: 14, Lines Deleted: 0; 1109 bytes
@@ -627,6 +627,20 @@
<listitem>
<para>
+ The <literal>INSERT_METHOD</literal> table option for a
+ <literal>MERGE</literal> table indicates which underlying
+ <literal>MyISAM</literal> table to use for inserts into the
+ <literal>MERGE</literal> table. However, use of the
+ <literal>AUTO_INCREMENT</literal> table option for that
+ <literal>MyISAM</literal> table has no effect for inserts into
+ the <literal>MERGE</literal> table until at least one row has
+ been inserted directly into the <literal>MyISAM</literal>
+ table.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
In MySQL 5.0.36 and later, the definition of the
<literal>MyISAM</literal> tables and the
<literal>MERGE</literal> table are checked when the tables are
Modified: trunk/refman-5.1/se-merge.xml
===================================================================
--- trunk/refman-5.1/se-merge.xml 2008-05-20 21:11:33 UTC (rev 10791)
+++ trunk/refman-5.1/se-merge.xml 2008-05-20 21:11:41 UTC (rev 10792)
Changed blocks: 1, Lines Added: 14, Lines Deleted: 0; 1109 bytes
@@ -619,6 +619,20 @@
<listitem>
<para>
+ The <literal>INSERT_METHOD</literal> table option for a
+ <literal>MERGE</literal> table indicates which underlying
+ <literal>MyISAM</literal> table to use for inserts into the
+ <literal>MERGE</literal> table. However, use of the
+ <literal>AUTO_INCREMENT</literal> table option for that
+ <literal>MyISAM</literal> table has no effect for inserts into
+ the <literal>MERGE</literal> table until at least one row has
+ been inserted directly into the <literal>MyISAM</literal>
+ table.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
In MySQL 5.1.15 and later, the definition of the
<literal>MyISAM</literal> tables and the
<literal>MERGE</literal> table are checked when the tables are
Modified: trunk/refman-6.0/se-merge.xml
===================================================================
--- trunk/refman-6.0/se-merge.xml 2008-05-20 21:11:33 UTC (rev 10791)
+++ trunk/refman-6.0/se-merge.xml 2008-05-20 21:11:41 UTC (rev 10792)
Changed blocks: 1, Lines Added: 14, Lines Deleted: 0; 1144 bytes
@@ -617,6 +617,20 @@
<listitem>
<para>
+ The <literal>INSERT_METHOD</literal> table option for a
+ <literal>MERGE</literal> table indicates which underlying
+ <literal>MyISAM</literal> table to use for inserts into the
+ <literal>MERGE</literal> table. However, use of the
+ <literal>AUTO_INCREMENT</literal> table option for that
+ <literal>MyISAM</literal> table has no effect for inserts into
+ the <literal>MERGE</literal> table until at least one row has
+ been inserted directly into the <literal>MyISAM</literal>
+ table.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
The definition of the <literal>MyISAM</literal> tables and the
<literal>MERGE</literal> table are checked when the tables are
accessed (for example, as part of a <literal>SELECT</literal>
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r10792 - in trunk: . it/refman-5.1 pt/refman-5.1 refman-4.1 refman-5.0 refman-5.1 refman-6.0 | paul | 20 May |
