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.3450 05/08/31 21:23:09 paul@stripped +2 -0
news-5.0.xml, news-4.1.xml:
Document bugfix. (Bug #12900)
news-5.0.xml:
Document bugfix. (Bug #11207)
news-4.1.xml:
Document bugfix. (Bug #9613)
news-5.0.xml:
Document bugfix. (Bug #10362)
news-4.1.xml, news-5.0.xml:
Document bugfix. (Bug #12537)
news-5.0.xml, news-4.1.xml:
Document bugfix. (Bug #12716)
Document bugfix. (Bug #12852)
news-4.1.xml:
Document bugfix. (Bug #12861)
refman-common/news-5.0.xml
1.124 05/08/31 21:18:47 paul@stripped +9 -0
Document bugfix. (Bug #12900)
refman-common/news-4.1.xml
1.70 05/08/31 21:18:47 paul@stripped +9 -0
Document bugfix. (Bug #12900)
refman-common/news-5.0.xml
1.123 05/08/31 21:15:20 paul@stripped +7 -0
Document bugfix. (Bug #11207)
refman-common/news-4.1.xml
1.69 05/08/31 21:13:08 paul@stripped +8 -0
Document bugfix. (Bug #9613)
refman-common/news-5.0.xml
1.122 05/08/31 21:09:57 paul@stripped +9 -0
Document bugfix. (Bug #10362)
refman-common/news-4.1.xml
1.68 05/08/31 21:05:16 paul@stripped +13 -0
Document bugfix. (Bug #12537)
refman-common/news-5.0.xml
1.121 05/08/31 21:04:07 paul@stripped +13 -0
Document bugfix. (Bug #12537)
refman-common/news-5.0.xml
1.120 05/08/31 20:56:16 paul@stripped +9 -0
Document bugfix. (Bug #12716)
refman-common/news-4.1.xml
1.67 05/08/31 20:56:16 paul@stripped +9 -0
Document bugfix. (Bug #12716)
refman-common/news-5.0.xml
1.119 05/08/31 20:49:58 paul@stripped +9 -0
Document bugfix. (Bug #12852)
refman-common/news-4.1.xml
1.66 05/08/31 20:49:58 paul@stripped +11 -2
Document bugfix. (Bug #12852)
refman-common/news-4.1.xml
1.65 05/08/31 20:45:08 paul@stripped +7 -0
Document bugfix. (Bug #12861)
# 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.64/refman-common/news-4.1.xml 2005-08-31 19:30:35 -05:00
+++ 1.70/refman-common/news-4.1.xml 2005-08-31 21:18:47 -05:00
@@ -180,6 +180,61 @@
<listitem>
<para>
+ The <literal>have_innodb</literal> read-only system variable
+ could not be selected with <literal>SELECT
+ @@have_innodb</literal>. (Bug #9613)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ A <literal>UNION</literal> of long <literal>utf8</literal>
+ <literal>VARCHAR</literal> columns was sometimes returned as a
+ column with a <literal>LONGTEXT</literal> data type rather
+ than <literal>VARCHAR</literal>. This could prevent such
+ queries from working at all if selected into a
+ <literal>MEMORY</literal> table because the
+ <literal>MEMORY</literal> storage engine does not support the
+ <literal>TEXT</literal> data types. (Bug #12537)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>NDB Cluster</literal>: When it could not copy a
+ fragment, <command>ndbd</command> exited without printing a
+ message about the condition to the error log. Now the message
+ is written. (Bug #12900)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>NDB Cluster</literal>: When a disk full condition
+ occurred, <command>ndbd</command> exited without printing a
+ message about the condition to the error log. Now the message
+ is written. (Bug #12716)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ If a client has opened an <literal>InnoDB</literal> table for
+ which the <filename>.ibd</filename> file is missing,
+ <literal>InnoDB</literal> would not honor a <literal>DROP
+ TABLE</literal> statement for the table. (Bug #12852)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>SELECT GROUP_CONCAT(...) FROM DUAL</literal> in a
+ subquery could cause the client to hang. (Bug #12861)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
<literal>NDB Cluster</literal>: Bad values in
<filename>config.ini</filename> caused
<command>ndb_mdmd</command> to crash. (Bug #12043)
--- 1.118/refman-common/news-5.0.xml 2005-08-31 19:51:02 -05:00
+++ 1.124/refman-common/news-5.0.xml 2005-08-31 21:18:47 -05:00
@@ -194,6 +194,37 @@
<listitem>
<para>
+ <literal>SHOW CREATE PROCEDURE</literal> and <literal>SHOW
+ CREATE FUNCTION</literal> no longer qualify the routine name
+ with the database name, for consistency with the behavior of
+ <literal>SHOW CREATE TABLE</literal>. (Bug #10362)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ A <literal>UNION</literal> of long <literal>utf8</literal>
+ <literal>VARCHAR</literal> columns was sometimes returned as a
+ column with a <literal>LONGTEXT</literal> data type rather
+ than <literal>VARCHAR</literal>. This could prevent such
+ queries from working at all if selected into a
+ <literal>MEMORY</literal> table because the
+ <literal>MEMORY</literal> storage engine does not support the
+ <literal>TEXT</literal> data types. (Bug #12537)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ If a client has opened an <literal>InnoDB</literal> table for
+ which the <filename>.ibd</filename> file is missing,
+ <literal>InnoDB</literal> would not honor a <literal>DROP
+ TABLE</literal> statement for the table. (Bug #12852)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
<literal>ALTER TABLE ... DISCARD TABLESPACE</literal> for a
<literal>MyISAM</literal> table caused the client to lose the
connection. (The server was not returning the error properly.)
@@ -384,6 +415,31 @@
</para>
<itemizedlist>
+
+ <listitem>
+ <para>
+ <literal>SET GLOBAL TRANSACTION ISOLATION LEVEL</literal> was
+ not working. (Bug #11207)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>NDB Cluster</literal>: When it could not copy a
+ fragment, <command>ndbd</command> exited without printing a
+ message about the condition to the error log. Now the message
+ is written. (Bug #12900)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>NDB Cluster</literal>: When a disk full condition
+ occurred, <command>ndbd</command> exited without printing a
+ message about the condition to the error log. Now the message
+ is written. (Bug #12716)
+ </para>
+ </listitem>
<listitem>
<para>
| Thread |
|---|
| • bk commit - mysqldoc@docsrva tree (paul:1.3450) | paul | 1 Sep |
