svn commit - mysqldoc@docsrva: r2023 - in trunk: refman-4.1 refman-5.0 refman-5.1 refman-common

[mcbrown]

Author: mcbrown
Date: 2006-05-04 12:51:04 +0200 (Thu, 04 May 2006)
New Revision: 2023

Log:
Documenting bug #18934 (InnoDB and reserved table names)



Modified:
   trunk/refman-4.1/innodb.xml
   trunk/refman-5.0/innodb.xml
   trunk/refman-5.1/innodb.xml
   trunk/refman-common/news-4.1.xml
   trunk/refman-common/news-5.0.xml
   trunk/refman-common/news-5.1.xml

Modified: trunk/refman-4.1/innodb.xml
===================================================================
--- trunk/refman-4.1/innodb.xml	2006-05-04 08:52:59 UTC (rev 2022)
+++ trunk/refman-4.1/innodb.xml	2006-05-04 10:51:04 UTC (rev 2023)
@@ -2449,6 +2449,17 @@
       </para>
 
       <para>
+        You cannot create a table with a name that matches the name of
+        an internal InnoDB table (including
+        <literal>DB_ROW_ID</literal>,
<literal>DB_TRX_ID</literal>,
+        <literal>DB_ROLL_PTR</literal> and
+        <literal>DB_MIX_ID</literal>). In versions of MySQL before
+        4.1.19 this would cause a crash, since 4.1.19 the server will
+        report error 1005 and refers to <literal>errno</literal> -1 in
+        the error message.
+      </para>
+
+      <para>
         <emphasis role="bold">Deviation from SQL standards</emphasis>:
         If there are several rows in the parent table that have the same
         referenced key value, <literal>InnoDB</literal> acts in foreign
@@ -6026,7 +6037,10 @@
           <para>
             Cannot create table. If the error message refers to
             <literal>errno</literal> 150, table creation failed because
-            a foreign key constraint was not correctly formed.
+            a foreign key constraint was not correctly formed. If the
+            error message refers to <literal>errno</literal> -1, table
+            creation probably failued because the table name matched the
+            name of an internal InnoDB table.
           </para>
         </listitem>
 

Modified: trunk/refman-5.0/innodb.xml
===================================================================
--- trunk/refman-5.0/innodb.xml	2006-05-04 08:52:59 UTC (rev 2022)
+++ trunk/refman-5.0/innodb.xml	2006-05-04 10:51:04 UTC (rev 2023)
@@ -6067,7 +6067,10 @@
           <para>
             Cannot create table. If the error message refers to
             <literal>errno</literal> 150, table creation failed because
-            a foreign key constraint was not correctly formed.
+            a foreign key constraint was not correctly formed. If the
+            error message refers to <literal>errno</literal> -1, table
+            creation probably failued because the table name matched the
+            name of an internal InnoDB table.
           </para>
         </listitem>
 
@@ -7261,6 +7264,19 @@
 
       <listitem>
         <para>
+          You cannot create a table with a name that matches the name of
+          an internal InnoDB table (including
+          <literal>DB_ROW_ID</literal>,
<literal>DB_TRX_ID</literal>,
+          <literal>DB_ROLL_PTR</literal> and
+          <literal>DB_MIX_ID</literal>). In versions of MySQL before
+          5.0.21 this would cause a crash, since 5.0.21 the server will
+          report error 1005 and refers to <literal>errno</literal> -1 in
+          the error message.
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
           As of MySQL 5.0.19, <literal>InnoDB</literal> does not ignore
           trailing spaces when comparing <literal>BINARY</literal> or
           <literal>VARBINARY</literal> column values. See

Modified: trunk/refman-5.1/innodb.xml
===================================================================
--- trunk/refman-5.1/innodb.xml	2006-05-04 08:52:59 UTC (rev 2022)
+++ trunk/refman-5.1/innodb.xml	2006-05-04 10:51:04 UTC (rev 2023)
@@ -2458,6 +2458,17 @@
       </para>
 
       <para>
+        You cannot create a table with a name that matches the name of
+        an internal InnoDB table (including
+        <literal>DB_ROW_ID</literal>,
<literal>DB_TRX_ID</literal>,
+        <literal>DB_ROLL_PTR</literal> and
+        <literal>DB_MIX_ID</literal>). In versions of MySQL before
+        5.1.10 this would cause a crash, since 5.1.101 the server will
+        report error 1005 and refers to <literal>errno</literal> -1 in
+        the error message.
+      </para>
+
+      <para>
         <emphasis role="bold">Deviation from SQL standards</emphasis>:
         If there are several rows in the parent table that have the same
         referenced key value, <literal>InnoDB</literal> acts in foreign
@@ -6015,7 +6026,10 @@
           <para>
             Cannot create table. If the error message refers to
             <literal>errno</literal> 150, table creation failed because
-            a foreign key constraint was not correctly formed.
+            a foreign key constraint was not correctly formed. If the
+            error message refers to <literal>errno</literal> -1, table
+            creation probably failued because the table name matched the
+            name of an internal InnoDB table.
           </para>
         </listitem>
 

Modified: trunk/refman-common/news-4.1.xml
===================================================================
--- trunk/refman-common/news-4.1.xml	2006-05-04 08:52:59 UTC (rev 2022)
+++ trunk/refman-common/news-4.1.xml	2006-05-04 10:51:04 UTC (rev 2023)
@@ -226,6 +226,18 @@
 
       <listitem>
         <para>
+          Creating a table in an InnoDB database that matched the name
+          of an internal InnoDB table (including
+          <literal>DB_ROW_ID</literal>,
<literal>DB_TRX_ID</literal>,
+          <literal>DB_ROLL_PTR</literal> and
+          <literal>DB_MIX_ID</literal>) would cause a crash. MySQL now
+          returns error 1005 (cannot create table) with
+          <literal>errno</literal> set to -1. (Bug #18934)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
           <emphasis role="bold">Security enhancement</emphasis>: Added
           the global <literal>max_prepared_stmt_count</literal> system
           variable to limit the total number of prepared statements in

Modified: trunk/refman-common/news-5.0.xml
===================================================================
--- trunk/refman-common/news-5.0.xml	2006-05-04 08:52:59 UTC (rev 2022)
+++ trunk/refman-common/news-5.0.xml	2006-05-04 10:51:04 UTC (rev 2023)
@@ -381,6 +381,18 @@
 
       <listitem>
         <para>
+          Creating a table in an InnoDB database that matched the name
+          of an internal InnoDB table (including
+          <literal>DB_ROW_ID</literal>,
<literal>DB_TRX_ID</literal>,
+          <literal>DB_ROLL_PTR</literal> and
+          <literal>DB_MIX_ID</literal>) would cause a crash. MySQL now
+          returns error 1005 (cannot create table) with
+          <literal>errno</literal> set to -1. (Bug #18934)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
           <literal>NDB Cluster</literal>: It is now possible to perform
           a partial start of a cluster. That is, it is now possible to
           bring up the cluster without running ndbd &ddash;initial on

Modified: trunk/refman-common/news-5.1.xml
===================================================================
--- trunk/refman-common/news-5.1.xml	2006-05-04 08:52:59 UTC (rev 2022)
+++ trunk/refman-common/news-5.1.xml	2006-05-04 10:51:04 UTC (rev 2023)
@@ -94,6 +94,18 @@
 
       <listitem>
         <para>
+          Creating a table in an InnoDB database that matched the name
+          of an internal InnoDB table (including
+          <literal>DB_ROW_ID</literal>,
<literal>DB_TRX_ID</literal>,
+          <literal>DB_ROLL_PTR</literal> and
+          <literal>DB_MIX_ID</literal>) would cause a crash. MySQL now
+          returns error 1005 (cannot create table) with
+          <literal>errno</literal> set to -1. (Bug #18934)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
           The <command>mysql_upgrade</command> command has been
           converted from a shell script to a C program, so it is
           available on non-Unix systems such as Windows. This program
@@ -211,12 +223,12 @@
           reporting this bug.
         </para>
       </listitem>
-      
+
       <listitem>
         <para>
           Event-creation statements enclosed in multi-line comments
           using <literal>/*!<replaceable>version_number</replaceable>
-            ... */</literal> syntax were not parsed correctly. (Bug
+          ... */</literal> syntax were not parsed correctly. (Bug
           #18078)
         </para>
       </listitem>