Author: paul
Date: 2005-11-02 21:57:00 +0100 (Wed, 02 Nov 2005)
New Revision: 224
Log:
r265@kite-hub: paul | 2005-11-02 14:56:51 -0600
InnoDB updates for AUTO_INCREMENT, max row size.
Modified:
trunk/
trunk/refman-4.1/innodb.xml
trunk/refman-5.0/innodb.xml
trunk/refman-5.1/innodb.xml
Property changes on: trunk
___________________________________________________________________
Name: svk:merge
- b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:3301
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:263
+ b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:3301
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:265
Modified: trunk/refman-4.1/innodb.xml
===================================================================
--- trunk/refman-4.1/innodb.xml 2005-11-02 20:03:06 UTC (rev 223)
+++ trunk/refman-4.1/innodb.xml 2005-11-02 20:57:00 UTC (rev 224)
@@ -1873,11 +1873,11 @@
Beginning with MySQL 4.1.12, <literal>InnoDB</literal> supports
the <literal>AUTO_INCREMENT =
<replaceable>n</replaceable></literal> table option in
- <literal>CREATE TABLE</literal> and <literal>ALTER
- TABLE</literal> statements, to set the initial counter value or
- alter the current counter value. The effect of this option is
- canceled by a server restart, for reasons discussed earlier in
- this section.
+ <literal>ALTER TABLE</literal> statements, to set the initial
+ counter value or alter the current counter value. The same is
+ true as of MySQL 4.1.14 for <literal>CREATE TABLE</literal>. The
+ effect of this option is canceled by a server restart, for
+ reasons discussed earlier in this section.
</para>
</section>
@@ -6949,10 +6949,11 @@
<listitem>
<para>
- <literal>InnoDB</literal> does not support the
- <literal>AUTO_INCREMENT</literal> table option for setting the
- initial sequence value in a <literal>CREATE TABLE</literal> or
- <literal>ALTER TABLE</literal> statement. To set the value
+ Before MySQL 4.1.12, <literal>InnoDB</literal> does not
+ support the <literal>AUTO_INCREMENT</literal> table option for
+ setting the initial sequence value in an <literal>ALTER
+ TABLE</literal> statement. Before MySQL 4.1.14, the same is
+ true for <literal>CREATE TABLE</literal>. To set the value
with <literal>InnoDB</literal>, insert a dummy row with a
value one less and delete that dummy row, or insert the first
row with an explicit value specified.
Modified: trunk/refman-5.0/innodb.xml
===================================================================
--- trunk/refman-5.0/innodb.xml 2005-11-02 20:03:06 UTC (rev 223)
+++ trunk/refman-5.0/innodb.xml 2005-11-02 20:57:00 UTC (rev 224)
@@ -6746,6 +6746,27 @@
<listitem>
<para>
+ Although <literal>InnoDB</literal> supports row sizes larger
+ than 65535 internally, you cannot define a row containing
+ <literal>VARCHAR</literal> columns with a combined size larger
+ than 65535:
+ </para>
+
+<programlisting>
+<!--
+mysql> DROP TABLE IF EXISTS t;
+-->
+mysql> <userinput>CREATE TABLE t (a VARCHAR(8000), b VARCHAR(10000),</userinput>
+ -> <userinput>c VARCHAR(10000), d VARCHAR(10000), e VARCHAR(10000),</userinput>
+ -> <userinput>f VARCHAR(10000), g VARCHAR(10000));</userinput>
+ERROR 1118 (42000): Row size too large. The maximum row size for the
+used table type, not counting BLOBs, is 65535. You have to change some
+columns to TEXT or BLOBs
+</programlisting>
+ </listitem>
+
+ <listitem>
+ <para>
On some older operating systems, data files must be less than
2GB.
</para>
@@ -6859,6 +6880,7 @@
<listitem>
<para>
+ In MySQL ¤t-series; before MySQL 5.0.3,
<literal>InnoDB</literal> does not support the
<literal>AUTO_INCREMENT</literal> table option for setting the
initial sequence value in a <literal>CREATE TABLE</literal> or
Modified: trunk/refman-5.1/innodb.xml
===================================================================
--- trunk/refman-5.1/innodb.xml 2005-11-02 20:03:06 UTC (rev 223)
+++ trunk/refman-5.1/innodb.xml 2005-11-02 20:57:00 UTC (rev 224)
@@ -6709,6 +6709,27 @@
<listitem>
<para>
+ Although <literal>InnoDB</literal> supports row sizes larger
+ than 65535 internally, you cannot define a row containing
+ <literal>VARCHAR</literal> columns with a combined size larger
+ than 65535:
+ </para>
+
+<programlisting>
+<!--
+mysql> DROP TABLE IF EXISTS t;
+-->
+mysql> <userinput>CREATE TABLE t (a VARCHAR(8000), b VARCHAR(10000),</userinput>
+ -> <userinput>c VARCHAR(10000), d VARCHAR(10000), e VARCHAR(10000),</userinput>
+ -> <userinput>f VARCHAR(10000), g VARCHAR(10000));</userinput>
+ERROR 1118 (42000): Row size too large. The maximum row size for the
+used table type, not counting BLOBs, is 65535. You have to change some
+columns to TEXT or BLOBs
+</programlisting>
+ </listitem>
+
+ <listitem>
+ <para>
On some older operating systems, data files must be less than
2GB.
</para>
@@ -6822,18 +6843,6 @@
<listitem>
<para>
- <literal>InnoDB</literal> does not support the
- <literal>AUTO_INCREMENT</literal> table option for setting the
- initial sequence value in a <literal>CREATE TABLE</literal> or
- <literal>ALTER TABLE</literal> statement. To set the value
- with <literal>InnoDB</literal>, insert a dummy row with a
- value one less and delete that dummy row, or insert the first
- row with an explicit value specified.
- </para>
- </listitem>
-
- <listitem>
- <para>
When you restart the MySQL server, <literal>InnoDB</literal>
may reuse an old value for an
<literal>AUTO_INCREMENT</literal> column (that is, a value
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r224 - in trunk: . refman-4.1 refman-5.0 refman-5.1 | paul | 2 Nov |
