Below is the list of changes that have just been committed into a local
mysqldoc repository of jan. When jan 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.3062 05/07/19 08:00:52 jan@stripped +1 -0
Added a note that consistent read does not work over DROP TABLE and
over ALTER TABLE (Bug #11981).
refman/innodb.xml
1.12 05/07/19 08:00:50 jan@stripped +13 -0
Added a note that consistent read does not work over DROP TABLE and
over ALTER TABLE (Bug #11981).
# 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: jan
# Host: hundin.mysql.fi
# Root: /home/jan/mysqldoc
--- 1.11/refman/innodb.xml 2005-07-14 23:11:33 +03:00
+++ 1.12/refman/innodb.xml 2005-07-19 08:00:50 +03:00
@@ -3619,6 +3619,19 @@
consistent read is being performed on the table.
</para>
+ <para>
+ Note that consistent read does not work over <literal>DROP
TABLE</literal>
+ and over <literal>ALTER TABLE</literal>. Consistent read does not work
+ over <literal>DROP TABLE</literal> because
<literal>MySQL</literal> can't
+ use table that has been dropped and <literal>InnoDB</literal> destroys
+ the table. Consistent read does not work over <literal>ALTER
TABLE</literal>
+ because it is executed inside of the transaction which creates a new table
+ and inserts rows from the old table to the new table. Now, when you reissue
+ the consistent read, it will not see any rows in the new table, because
+ they were inserted in a transaction that is not visible in the snapshot
+ that the consistent read reads.
+ </para>
+
</section>
<section id="innodb-locking-reads">
| Thread |
|---|
| • bk commit - mysqldoc@docsrva tree (jan:1.3062) | Jan Lindstrom | 19 Jul |