Below is the list of changes that have just been committed into a local
mysqldoc repository of root. When root 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.3192 05/08/08 10:29:14 Mike.Hillyer@stripped +3 -0
Bugs documented: 12154,12095,11869,10473,9459,12348,6859
refman-common/news-5.0.xml
1.25 05/08/08 10:29:13 Mike.Hillyer@stripped +77 -25
Document bugfixes
refman-common/news-4.1.xml
1.17 05/08/08 10:29:13 Mike.Hillyer@stripped +32 -0
Document bugfixes
refman-common/news-4.0.xml
1.6 05/08/08 10:29:13 Mike.Hillyer@stripped +13 -6
Document bugfixes
# 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: Mike.Hillyer
# Host: www.openwin.org
# Root: /home/mysqldoc/mysqldoc
--- 1.5/refman-common/news-4.0.xml 2005-08-04 04:12:23 -06:00
+++ 1.6/refman-common/news-4.0.xml 2005-08-08 10:29:13 -06:00
@@ -153,11 +153,18 @@
</para>
<itemizedlist>
-
+
<listitem>
<para>
- On AMD64, attempting to repair a <literal>MyISAM</literal>
- table with a full-text index would crash the server. (Bug
+ Addition of <literal>mysql</literal> group failed on CentOS
+ install. (Bug #12348)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ On AMD64, attempting to repair a <literal>MyISAM</literal>
+ table with a full-text index would crash the server. (Bug
#11684)
</para>
</listitem>
@@ -892,11 +899,11 @@
</para>
<itemizedlist>
-
+
<listitem>
<para>
- A multi-table <literal>DELETE</literal> could cause MySQL to
- crash when using <literal>InnoDB</literal> tables. (Bug #5837,
+ A multi-table <literal>DELETE</literal> could cause MySQL to
+ crash when using <literal>InnoDB</literal> tables. (Bug #5837,
Bug #6378)
</para>
</listitem>
--- 1.16/refman-common/news-4.1.xml 2005-08-06 20:16:35 -06:00
+++ 1.17/refman-common/news-4.1.xml 2005-08-08 10:29:13 -06:00
@@ -233,6 +233,38 @@
<listitem>
<para>
+ Addition of <literal>mysql</literal> group failed on CentOS
+ install. (Bug #12348)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>FLUSH TABLES WITH READ LOCK</literal> combined with
+ <literal>LOCK TABLE .. WRITE</literal> caused deadlock. (Bug
+ #9459)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>GROUP_CONCAT</literal> ignores the
+ <literal>DISTINCT</literal> modifier when used in a query
+ joining multiple tables where one of the tables has a single
+ row. (Bug #12095)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>UNION</literal> query with
+ <literal>FULLTEXT</literal> could cause server crash. (Bug
+ #11869)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
Performing <literal>DATE(LEFT(column,8))</literal> on a
<literal>DATE</literal> column produces incorrect results.
(Bug #12266)
--- 1.24/refman-common/news-5.0.xml 2005-08-06 20:19:10 -06:00
+++ 1.25/refman-common/news-5.0.xml 2005-08-08 10:29:13 -06:00
@@ -174,7 +174,12 @@
<itemizedlist>
<listitem>
- <para></para>
+ <para>
+ Trying to drop the default keycache by setting
+ <literal>@@global.key_buffer_size</literal> to zero now
+ returns a warning that the default keycache cannot be dropped.
+ (Bug #10473)
+ </para>
</listitem>
</itemizedlist>
@@ -200,6 +205,38 @@
</para>
</listitem>
+ <listitem>
+ <para>
+ <literal>FLUSH TABLES WITH READ LOCK</literal> combined with
+ <literal>LOCK TABLE .. WRITE</literal> caused deadlock. (Bug
+ #9459)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>NULL</literal> column definitions read incorrectly
+ for inner tables of nested outer joins. (Bug #12154)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>GROUP_CONCAT</literal> ignores the
+ <literal>DISTINCT</literal> modifier when used in a query
+ joining multiple tables where one of the tables has a single
+ row. (Bug #12095)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>UNION</literal> query with
+ <literal>FULLTEXT</literal> could cause server crash. (Bug
+ #11869)
+ </para>
+ </listitem>
+
</itemizedlist>
</section>
@@ -273,6 +310,14 @@
</para>
</listitem>
+ <listitem>
+ <para>
+ Added error message for users who attempt <literal>CREATE
+ TABLE ... LIKE</literal> and specify a non-table in the
+ <literal>LIKE</literal> clause. (Bug #6859)
+ </para>
+ </listitem>
+
</itemizedlist>
<para>
@@ -283,6 +328,13 @@
<listitem>
<para>
+ Addition of <literal>mysql</literal> group failed on CentOS
+ install. (Bug #12348)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
<literal>big5</literal> strings were not being stored in
<literal>FULLTEXT</literal> index. (Bug #12075)
</para>
@@ -4812,21 +4864,21 @@
<listitem>
<para>
- <literal>InnoDB</literal>: Introduced a compact record format
- that does not store the number of columns or the lengths of
- fixed-size columns. The old format can be requested by
- specifying <literal>ROW_FORMAT=REDUNDANT</literal>. The new
- format (<literal>ROW_FORMAT=COMPACT</literal>) is the default.
+ <literal>InnoDB</literal>: Introduced a compact record format
+ that does not store the number of columns or the lengths of
+ fixed-size columns. The old format can be requested by
+ specifying <literal>ROW_FORMAT=REDUNDANT</literal>. The new
+ format (<literal>ROW_FORMAT=COMPACT</literal>) is the default.
The new format typically saves 20 % of disk space and memory.
</para>
</listitem>
<listitem>
<para>
- <literal>InnoDB</literal>: Setting the initial
- <literal>AUTO_INCREMENT</literal> value for an
- <literal>InnoDB</literal> table using <literal>CREATE TABLE
- ... AUTO_INCREMENT = <replaceable>n</replaceable></literal>
+ <literal>InnoDB</literal>: Setting the initial
+ <literal>AUTO_INCREMENT</literal> value for an
+ <literal>InnoDB</literal> table using <literal>CREATE TABLE
+ ... AUTO_INCREMENT = <replaceable>n</replaceable></literal>
now works, and <literal>ALTER TABLE ... AUTO_INCREMENT =
<replaceable>n</replaceable></literal> resets the current
value.
@@ -4974,21 +5026,21 @@
so you can't replicate such statements from a 5.0.3 master to
pre-5.0.3 slaves.
</para>
- </listitem>
-
- <listitem>
- <para>
- <literal>NDB Cluster</literal>: When using this storage
- engine, the output of <literal>SHOW TABLE STATUS</literal>
- now displays properly-calculated values in the
- <literal>Avg_row_length</literal> and
- <literal>Data_length</literal> columns. (Note that
- <literal>BLOB</literal> columns are not yet taken into
- account.) In addition, the number of replicas is now shown
- in the <literal>Comment</literal> column (as
- <literal>number_of_replicas</literal>).
- </para>
- </listitem>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>NDB Cluster</literal>: When using this storage
+ engine, the output of <literal>SHOW TABLE STATUS</literal> now
+ displays properly-calculated values in the
+ <literal>Avg_row_length</literal> and
+ <literal>Data_length</literal> columns. (Note that
+ <literal>BLOB</literal> columns are not yet taken into
+ account.) In addition, the number of replicas is now shown in
+ the <literal>Comment</literal> column (as
+ <literal>number_of_replicas</literal>).
+ </para>
+ </listitem>
</itemizedlist>
| Thread |
|---|
| • bk commit - mysqldoc@docsrva tree (Mike.Hillyer:1.3192) | mhillyer | 8 Aug |
