Below is the list of changes that have just been committed into a local
mysqldoc repository of paul. When paul 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.3444 05/08/31 12:54:45 paul@stripped +4 -0
Add InnoDB troubleshooting hint.
refman/innodb.xml
1.31 05/08/31 12:54:43 paul@stripped +10 -2
Add InnoDB troubleshooting hint.
refman-5.1/innodb.xml
1.17 05/08/31 12:54:43 paul@stripped +11 -3
Sync.
refman-5.0/innodb.xml
1.17 05/08/31 12:54:43 paul@stripped +65 -24
Sync.
refman-4.1/innodb.xml
1.25 05/08/31 12:54:43 paul@stripped +10 -2
Sync.
# 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: paul
# Host: frost.snake.net
# Root: /Volumes/frost2/MySQL/bk/mysqldoc
--- 1.16/refman-5.1/innodb.xml 2005-08-31 11:15:19 -05:00
+++ 1.17/refman-5.1/innodb.xml 2005-08-31 12:54:43 -05:00
@@ -1918,8 +1918,8 @@
<para>
In the referencing table, there must be an index where the
foreign key columns are listed as the
- <emphasis>first</emphasis> columns in the same order.
- Such an index will be created on the referencing table
+ <emphasis>first</emphasis> columns in the same order. Such
+ an index will be created on the referencing table
automatically if it does not exist.
</para>
</listitem>
@@ -6965,7 +6965,15 @@
<para>
You can drop the orphaned table by following the instructions
- given in the error message.
+ given in the error message. If you are still unable to use
+ <literal>DROP TABLE</literal> successfully, the problem may be
+ due to name completion in the <command>mysql</command> client.
+ To work around this, start the <command>mysql</command> client
+ with the <option>--disable-auto-rehash</option> option and try
+ <literal>DROP TABLE</literal> again. (With name completion on,
+ <command>mysql</command> tries to construct a list of table
+ names, which doesn't work when a problem such as just described
+ exists.)
</para>
<para>
--- 1.24/refman-4.1/innodb.xml 2005-08-31 11:15:19 -05:00
+++ 1.25/refman-4.1/innodb.xml 2005-08-31 12:54:43 -05:00
@@ -2043,7 +2043,7 @@
foreign key columns are listed as the
<emphasis>first</emphasis> columns in the same order.
Starting with MySQL/InnoDB 4.1.2, such an index will be
- created on the referencing table automatically if it does
+ created on the referencing table automatically if it does
not exist.
</para>
</listitem>
@@ -7224,7 +7224,15 @@
<para>
You can drop the orphaned table by following the instructions
- given in the error message.
+ given in the error message. If you are still unable to use
+ <literal>DROP TABLE</literal> successfully, the problem may be
+ due to name completion in the <command>mysql</command> client.
+ To work around this, start the <command>mysql</command> client
+ with the <option>--disable-auto-rehash</option> option and try
+ <literal>DROP TABLE</literal> again. (With name completion on,
+ <command>mysql</command> tries to construct a list of table
+ names, which doesn't work when a problem such as just described
+ exists.)
</para>
<para>
--- 1.30/refman/innodb.xml 2005-08-31 11:15:23 -05:00
+++ 1.31/refman/innodb.xml 2005-08-31 12:54:43 -05:00
@@ -2025,7 +2025,7 @@
foreign key columns are listed as the
<emphasis>first</emphasis> columns in the same order.
Starting with MySQL/InnoDB 4.1.2, such an index will be
- created on the referencing table automatically if it does
+ created on the referencing table automatically if it does
not exist.
</para>
</listitem>
@@ -7198,7 +7198,15 @@
<para>
You can drop the orphaned table by following the instructions
- given in the error message.
+ given in the error message. If you are still unable to use
+ <literal>DROP TABLE</literal> successfully, the problem may be
+ due to name completion in the <command>mysql</command> client.
+ To work around this, start the <command>mysql</command> client
+ with the <option>--disable-auto-rehash</option> option and try
+ <literal>DROP TABLE</literal> again. (With name completion on,
+ <command>mysql</command> tries to construct a list of table
+ names, which doesn't work when a problem such as just described
+ exists.)
</para>
<para>
--- 1.16/refman-5.0/innodb.xml 2005-08-31 11:15:19 -05:00
+++ 1.17/refman-5.0/innodb.xml 2005-08-31 12:54:43 -05:00
@@ -26,9 +26,11 @@
<secondary><literal>InnoDB</literal></secondary>
</indexterm>
-<remark role="todo">A number of node names in this chapter are very generic
- (e.g., "Backing up" and could apply in non-InnoDB contexts. Might
- be best to rename a bunch of them.</remark>
+ <remark role="todo">
+ A number of node names in this chapter are very generic (e.g.,
+ "Backing up" and could apply in non-InnoDB contexts. Might be best
+ to rename a bunch of them.
+ </remark>
<section id="innodb-overview">
@@ -423,8 +425,10 @@
like.
</para>
-<remark role="todo">Do we really need this info here, since it just repeats
- what's found in the Installation and other chapters? /JS</remark>
+ <remark role="todo">
+ Do we really need this info here, since it just repeats what's
+ found in the Installation and other chapters? /JS
+ </remark>
<para>
<emphasis role="bold">Where to specify options on
@@ -655,7 +659,9 @@
<title id="title-innodb-start">&title-innodb-start;</title>
-<remark role="todo">Have separate lists for options and variables?</remark>
+ <remark role="todo">
+ Have separate lists for options and variables?
+ </remark>
<para>
This section describes the <literal>InnoDB</literal>-related
@@ -664,7 +670,9 @@
form on the command line or in option files.
</para>
-<remark role="todo">these should be listed using -opt_name=type_of_value syntax</remark>
+ <remark role="todo">
+ these should be listed using -opt_name=type_of_value syntax
+ </remark>
<itemizedlist>
@@ -850,8 +858,10 @@
<literal>innodb_file_per_table</literal>
</para>
-<remark role="todo">Determine if this bug exists in 5.0.x and handle the
- following accordingly</remark>
+ <remark role="todo">
+ Determine if this bug exists in 5.0.x and handle the following
+ accordingly
+ </remark>
<!--
<para>
@@ -1297,7 +1307,9 @@
</listitem>
<listitem>
-<remark role="todo">document innodb_sync_spin_loops</remark>
+ <remark role="todo">
+ document innodb_sync_spin_loops
+ </remark>
<para>
<literal>innodb_safe_binlog</literal>
@@ -1368,7 +1380,9 @@
</listitem>
<listitem>
-<remark role="todo">document innodb_thread_sleep_delay</remark>
+ <remark role="todo">
+ document innodb_thread_sleep_delay
+ </remark>
<para>
<literal>innodb_status_file</literal>
@@ -1864,7 +1878,10 @@
<title id="title-innodb-foreign-key-constraints">&title-innodb-foreign-key-constraints;</title>
-<remark>description_for_help_topic CONSTRAINT FOREIGN KEY REFERENCES NO ACTION ON DELETE CASCADE SET NULL RESTRICT UPDATE</remark>
+ <remark>
+ description_for_help_topic CONSTRAINT FOREIGN KEY REFERENCES NO
+ ACTION ON DELETE CASCADE SET NULL RESTRICT UPDATE
+ </remark>
<para>
<literal>InnoDB</literal> also supports foreign key constraints.
@@ -1879,7 +1896,9 @@
[ON UPDATE {RESTRICT | CASCADE | SET NULL | NO ACTION}]
</programlisting>
-<remark>end_description_for_help_topic</remark>
+ <remark>
+ end_description_for_help_topic
+ </remark>
<para>
Foreign keys definitions are subject to the following
@@ -1899,8 +1918,8 @@
<para>
In the referencing table, there must be an index where the
foreign key columns are listed as the
- <emphasis>first</emphasis> columns in the same order.
- Such an index will be created on the referencing table
+ <emphasis>first</emphasis> columns in the same order. Such
+ an index will be created on the referencing table
automatically if it does not exist.
</para>
</listitem>
@@ -1955,7 +1974,9 @@
<itemizedlist>
-<remark role="todo">Rewrite following paragraph to make clearer.</remark>
+ <remark role="todo">
+ Rewrite following paragraph to make clearer.
+ </remark>
<listitem>
<para>
@@ -2156,7 +2177,9 @@
single-column index in the <literal>customer</literal> table:
</para>
-<remark>example_for_help_topic CONSTRAINT</remark>
+ <remark>
+ example_for_help_topic CONSTRAINT
+ </remark>
<programlisting>
CREATE TABLE product (
@@ -2272,7 +2295,9 @@
<literal>lower_case_table_names</literal> system variable.
</para>
-<remark>Does this still apply in 5.0?</remark>
+ <remark>
+ Does this still apply in 5.0?
+ </remark>
<!--
<para>
@@ -2379,7 +2404,9 @@
<title id="title-innodb-and-mysql-replication">&title-innodb-and-mysql-replication;</title>
-<remark role="todo">Add xref to here from replication chapter.</remark>
+ <remark role="todo">
+ Add xref to here from replication chapter.
+ </remark>
<para>
MySQL replication works for <literal>InnoDB</literal> tables as
@@ -3910,7 +3937,9 @@
.
</para>
-<remark role="todo">More ASCII art that needs to be turned into a graphic.</remark>
+ <remark role="todo">
+ More ASCII art that needs to be turned into a graphic.
+ </remark>
<programlisting>
User A User B
@@ -4131,8 +4160,10 @@
<title id="title-innodb-implicit-command-or-rollback">&title-innodb-implicit-command-or-rollback;</title>
-<remark role="todo">Probably should merge this into the SQL chapter section that
- also lists these conditions.</remark>
+ <remark role="todo">
+ Probably should merge this into the SQL chapter section that
+ also lists these conditions.
+ </remark>
<para>
MySQL begins each client connection with autocommit mode enabled
@@ -6550,7 +6581,9 @@
<title id="title-innodb-restrictions">&title-innodb-restrictions;</title>
-<remark role="todo">Move this info to new Restrictions appendix?</remark>
+ <remark role="todo">
+ Move this info to new Restrictions appendix?
+ </remark>
<itemizedlist>
@@ -6932,7 +6965,15 @@
<para>
You can drop the orphaned table by following the instructions
- given in the error message.
+ given in the error message. If you are still unable to use
+ <literal>DROP TABLE</literal> successfully, the problem may be
+ due to name completion in the <command>mysql</command> client.
+ To work around this, start the <command>mysql</command> client
+ with the <option>--disable-auto-rehash</option> option and try
+ <literal>DROP TABLE</literal> again. (With name completion on,
+ <command>mysql</command> tries to construct a list of table
+ names, which doesn't work when a problem such as just described
+ exists.)
</para>
<para>
| Thread |
|---|
| • bk commit - mysqldoc@docsrva tree (paul:1.3444) | paul | 31 Aug |
