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.3669 05/10/06 10:36:39 paul@stripped +3 -0
news-5.0.xml, news-4.1.xml:
Document bugfix. (Bug#12669)
news-4.1.xml, news-5.0.xml:
Revise changelog entries
news-4.1.xml, news-4.0.xml, news-5.0.xml:
Document bugfix. (Bug#13002)
news-5.0.xml:
Document bugfix. (Bug#12334)
refman-common/news-5.0.xml
1.264 05/10/06 10:36:28 paul@stripped +8 -0
Document bugfix. (Bug#12669)
refman-common/news-4.1.xml
1.124 05/10/06 10:36:28 paul@stripped +8 -0
Document bugfix. (Bug#12669)
refman-common/news-4.1.xml
1.123 05/10/06 10:26:19 paul@stripped +4 -4
Revise changelog entries
refman-common/news-5.0.xml
1.263 05/10/06 10:26:18 paul@stripped +6 -7
Revise changelog entries
refman-common/news-4.1.xml
1.122 05/10/06 09:56:45 paul@stripped +10 -0
Document bugfix. (Bug#13002)
refman-common/news-4.0.xml
1.37 05/10/06 09:56:45 paul@stripped +10 -0
Document bugfix. (Bug#13002)
refman-common/news-5.0.xml
1.262 05/10/06 09:56:44 paul@stripped +10 -0
Document bugfix. (Bug#13002)
refman-common/news-5.0.xml
1.261 05/10/06 08:22:10 paul@stripped +8 -0
Document bugfix. (Bug#12334)
# 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: /Users/paul/bk/mysqldoc
--- 1.36/refman-common/news-4.0.xml 2005-10-05 19:34:31 -05:00
+++ 1.37/refman-common/news-4.0.xml 2005-10-06 09:56:45 -05:00
@@ -162,6 +162,16 @@
<listitem>
<para>
+ <literal>SHOW CREATE TABLE</literal> did not display any
+ <literal>FOREIGN KEY</literal> clauses if a temporary file
+ could not be created. Now <literal>SHOW CREATE TABLE</literal>
+ displays an error message in an SQL comment if this occurs.
+ (Bug #13002)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
MySQL programs in binary distributions for Solaris 8/9/10 x86
systems would not run on Pentium III machines. (Bug #6772)
</para>
--- 1.121/refman-common/news-4.1.xml 2005-10-05 20:08:29 -05:00
+++ 1.124/refman-common/news-4.1.xml 2005-10-06 10:36:28 -05:00
@@ -226,10 +226,28 @@
<listitem>
<para>
- <literal>SHOW CREATE TABLE</literal> failed to display the
- <literal>AUTO_INCREMENT</literal> attribute for an
- <literal>AUTO_INCREMENT</literal> column if
- <literal>ANSI</literal> SQL mode was enabled. (Bug #7977)
+ <literal>CHECKSUM TABLE</literal> locked
+ <literal>InnoDB</literal> tables and did not use a consistent
+ read. (Bug #12669)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>SHOW CREATE TABLE</literal> did not display any
+ <literal>FOREIGN KEY</literal> clauses if a temporary file
+ could not be created. Now <literal>SHOW CREATE TABLE</literal>
+ displays an error message in an SQL comment if this occurs.
+ (Bug #13002)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Display of the <literal>AUTO_INCREMENT</literal> attribute by
+ <literal>SHOW CREATE TABLE</literal> was not controlled by the
+ <literal>NO_FIELD_OPTIONS</literal> SQL mode as it should have
+ been. (Bug #7977)
</para>
</listitem>
--- 1.260/refman-common/news-5.0.xml 2005-10-05 20:27:30 -05:00
+++ 1.264/refman-common/news-5.0.xml 2005-10-06 10:36:28 -05:00
@@ -181,6 +181,16 @@
<listitem>
<para>
+ <literal>SHOW CREATE TABLE</literal> did not display any
+ <literal>FOREIGN KEY</literal> clauses if a temporary file
+ could not be created. Now <literal>SHOW CREATE TABLE</literal>
+ displays an error message in an SQL comment if this occurs.
+ (Bug #13002)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
A column in the <literal>ON</literal> condition of a join that
referenced a table in a nested join could not be resolved if
the nested join was a right join. (Bug #13597)
@@ -341,6 +351,14 @@
<listitem>
<para>
+ <literal>CHECKSUM TABLE</literal> locked
+ <literal>InnoDB</literal> tables and did not use a consistent
+ read. (Bug #12669)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
The <option>--skip-doublewrite-buffer</option> disables use of
the <literal>InnoDB</literal> doublewrite buffer. But having
the option in effect when creating a new MySQL installation
@@ -358,13 +376,12 @@
<listitem>
<para>
- With <literal>LOCK TABLES</literal> in effect,
- <literal>InnoDB</literal> executed <literal>SELECT ... FOR
- UPDATE</literal> and <literal>SELECT ... LOCK IN SHARE
- MODE</literal> as non-locking consistent reads, rather than
- locking with exclusive locks.. This also occurred within
- stored functions or triggers, and stored procedures called
- from stored functions or triggers. (Bug #11238)
+ With <literal>LOCK TABLES</literal> in effect, when
+ <literal>SELECT ... FOR UPDATE</literal> or <literal>SELECT
+ ... LOCK IN SHARE MODE</literal> for an
+ <literal>InnoDB</literal> table were executed from within a
+ stored function or a trigger, they were converted to a
+ non-locking consistent read. (Bug #11238)
</para>
</listitem>
@@ -1412,6 +1429,14 @@
An optimizer estimate of zero rows for a non-empty
<literal>InnoDB</literal> table used in a left or right join
could cause incomplete rollback for the table. (Bug #12779)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Calls to stored procedures were written to the binary log even
+ within transactions that were rolled back, causing them to be
+ executed on replication slaves. (Bug #12334)
</para>
</listitem>
| Thread |
|---|
| • bk commit - mysqldoc@docsrva tree (paul:1.3669) | paul | 6 Oct |
