Author: jstephens
Date: 2007-10-26 13:46:37 +0200 (Fri, 26 Oct 2007)
New Revision: 8339
Log:
Consolidated some more changelog entries. Updated duplicates list.
Modified:
trunk/dynamic-docs/changelog/dupes.txt
trunk/dynamic-docs/changelog/mysqld.xml
Modified: trunk/dynamic-docs/changelog/dupes.txt
===================================================================
--- trunk/dynamic-docs/changelog/dupes.txt 2007-10-26 09:41:56 UTC (rev 8338)
+++ trunk/dynamic-docs/changelog/dupes.txt 2007-10-26 11:46:37 UTC (rev 8339)
Changed blocks: 4, Lines Added: 18, Lines Deleted: 17; 683 bytes
@@ -23,21 +23,21 @@
5949x
5998x
6172x
-6505
-6554
-6558
-6883
+6505x
+6554x
+6558x
+6883x
6895x
-7061
-7115
-7142
-7249
-7344
-7350
-7358
-7425
-7815
-7879
+7061x
+7115x
+7142x
+7249x
+7344x
+7350x
+7358x
+7425x
+7815x
+7879x
7894
7965
7975
@@ -51,7 +51,7 @@
8406
8663
8681
-8771
+8771x
8841
9148
9286
@@ -95,7 +95,7 @@
12385
12476x
12480
-12817
+12817x
12982
12991
13159
@@ -370,4 +370,5 @@
30624
30681
30764
-30914
\ No newline at end of file
+30914
+
Modified: trunk/dynamic-docs/changelog/mysqld.xml
===================================================================
--- trunk/dynamic-docs/changelog/mysqld.xml 2007-10-26 09:41:56 UTC (rev 8338)
+++ trunk/dynamic-docs/changelog/mysqld.xml 2007-10-26 11:46:37 UTC (rev 8339)
Changed blocks: 43, Lines Added: 194, Lines Deleted: 415; 22663 bytes
@@ -1470,33 +1470,6 @@
<logentry entrytype="bug">
<tags>
- <manual type="InnoDB"/>
- <manual type="character sets"/>
- </tags>
-
- <bugs>
- <fixes bugid="8771"/>
- <fixes bugid="7350"/>
- </bugs>
-
- <versions>
- <version ver="5.0.3"/>
- </versions>
-
- <message>
-
- <para>
- <literal>InnoDB</literal>: Corrected the handling of trailing
- spaces in the <literal>ucs2</literal> character set.
- </para>
-
- </message>
-
- </logentry>
-
- <logentry entrytype="bug">
-
- <tags>
<manual type="SET"/>
<manual type="stored routine"/>
</tags>
@@ -2098,13 +2071,16 @@
<bugs>
<fixes bugid="7249"/>
+ <seealsobug bugid="7518"/>
</bugs>
<versions>
<version ver="4.1.9"/>
+ <version ver="4.1.14"/>
+ <version ver="5.0.10"/>
</versions>
- <message>
+ <message ver="4.1.9">
<para>
<command>mysqld_safe</command> no longer tests for the presence
@@ -2117,6 +2093,17 @@
</message>
+ <message>
+
+ <para>
+ The MySQL server now starts correctly with all combinations of
+ <literal>basedir</literal> and <literal>datadir</literal>
+ resolving an issue introduced by the original fix for this bug
+ in MySQL 4.1.9.
+ </para>
+
+ </message>
+
</logentry>
<logentry entrytype="bug">
@@ -11338,37 +11325,6 @@
<logentry entrytype="bug">
<tags>
- <manual type="MyISAM"/>
- <manual type="DELETE"/>
- <manual type="UPDATE"/>
- </tags>
-
- <bugs>
- <fixes bugid="7879"/>
- </bugs>
-
- <versions>
- <version ver="4.1.10"/>
- </versions>
-
- <message>
-
- <para>
- InnoDB: Fix a theoretical hang over the adaptive hash latch in
- InnoDB if one runs <literal>INSERT ... SELECT ...</literal>
- (binlog not enabled), or a multiple-table
- <literal>UPDATE</literal> or <literal>DELETE</literal>, and only
- the read tables are InnoDB type, the rest are
- <literal>MyISAM</literal>.
- </para>
-
- </message>
-
- </logentry>
-
- <logentry entrytype="bug">
-
- <tags>
<manual type="fno-common"/>
<manual type="Mac OS X"/>
</tags>
@@ -12010,6 +11966,7 @@
<versions>
<version ver="4.1.9"/>
+ <version ver="5.0.3"/>
</versions>
<message>
@@ -14603,6 +14560,10 @@
<tags>
<manual type="binary log"/>
+ <manual type="MyISAM"/>
+ <manual type="DELETE"/>
+ <manual type="UPDATE"/>
+ <manual type="InnoDB"/>
</tags>
<bugs>
@@ -14617,11 +14578,10 @@
<message>
<para>
- Fixed a bug where MySQL was allowing concurrent updates
- (inserts, deletes) to a table if binary logging is enabled.
- Changed to ensure that all updates are executed in a serialized
- fashion, because they are executed serialized when binlog is
- replayed.
+ MySQL allowed concurrent updates (including inserts and deletes)
+ to a table if binary logging was enabled. Now, all updates are
+ executed in a serialized fashion, because they are executed
+ serialized when the binlog is replayed.
</para>
</message>
@@ -17256,19 +17216,31 @@
<versions>
<version ver="5.0.7"/>
+ <version ver="5.0.14"/>
</versions>
- <message>
+ <message ver="5.0.7">
<para>
The <option>--delayed-insert</option> option for
- <command>mysqldump</command> has been disabled to avoid causing
+ <command>mysqldump</command> was disabled to avoid causing
problems with storage engines that do not support
<literal>INSERT DELAYED</literal>.
</para>
</message>
+ <message ver="5.0.14">
+
+ <para>
+ Re-enabled the <option>--delayed-inserts</option> option for
+ <command>mysqldump</command>, which now checks for each table
+ dumped whether its storage engine supports
+ <literal>DELAYED</literal> inserts.
+ </para>
+
+ </message>
+
</logentry>
<logentry entrytype="feature">
@@ -19039,9 +19011,10 @@
<versions>
<version ver="4.1.11"/>
+ <version ver="4.1.12"/>
</versions>
- <message>
+ <message ver="4.1.11">
<para>
Changed <literal>mysql_server_end()</literal> C API function to
@@ -19052,6 +19025,17 @@
</message>
+ <message ver="4.1.12">
+
+ <para>
+ Additional fix for <literal>mysql_server_init()</literal> and
+ <literal>mysql_server_end()</literal> C API functions so that
+ stopping and restarting the embedded server would not cause a
+ crash.
+ </para>
+
+ </message>
+
</logentry>
<logentry entrytype="bug">
@@ -19172,24 +19156,39 @@
<bugs>
<fixes bugid="7142"/>
- <fixes bugid="12817"/>
+ <seealsobug bugid="12817"/>
</bugs>
<versions>
<version ver="4.1.13"/>
+ <version ver="5.0.13"/>
</versions>
- <message>
+ <message ver="4.1.13">
<para>
<literal>SHOW FIELDS</literal> truncated the
- <literal>TYPE</literal> column to 40 characters. (Note: This fix
- was reverted in MySQL 4.1.15 because it broke existing
- applications.)
+ <literal>TYPE</literal> column to 40 characters.
</para>
+ <note>
+ <para>
+ This fix was reverted in MySQL 4.1.15 because it broke
+ existing applications.
+ </para>
+ </note>
+
</message>
+ <message ver="5.0.13">
+
+ <para>
+ <literal>SHOW FIELDS</literal> truncated the
+ <literal>TYPE</literal> column to 40 characters.
+ </para>
+
+ </message>
+
</logentry>
<logentry entrytype="bug">
@@ -22539,9 +22538,10 @@
</logentry>
- <logentry entrytype="feature">
+ <logentry entrytype="bug">
<tags>
+ <manual type="CHECK TABLE"/>
<manual type="collation"/>
</tags>
@@ -22556,9 +22556,18 @@
<message>
<para>
- Added <literal>cp1250_croatian_ci</literal> collation.
+ The <literal>latin2_croatian_ci</literal> collation was not
+ sorted correctly. After upgrading to MySQL 4.1.12, all tables
+ that have indexes using this collation are treated as crashed;
+ for each such table, you must use <literal>CHECK TABLE</literal>
+ and possibly repair the table.
</para>
+ <para>
+ Support for the <literal>cp1250_croatian_ci</literal> collation
+ was also added as part of the fix for this bug.
+ </para>
+
</message>
</logentry>
@@ -27962,6 +27971,8 @@
<manual type="JOIN"/>
<manual type="NATURAL"/>
<manual type="USING"/>
+ <manual type="views"/>
+ <highlight type="incompatiblechange"/>
</tags>
<bugs>
@@ -27987,8 +27998,7 @@
<message>
<para>
- <emphasis role="bold">Incompatible change:</emphasis> Beginning
- with MySQL 5.0.12, natural joins and joins with
+ Beginning with MySQL 5.0.12, natural joins and joins with
<literal>USING</literal>, including outer join variants, are
processed according to the SQL:2003 standard. The changes
include elimination of redundant output columns for
@@ -27999,6 +28009,14 @@
</para>
<para>
+ In addition, a <errortext>Duplicate column name
+ error</errortext> no longer occurs when selecting from a view
+ defined as <literal>SELECT *</literal> from a join that uses a
+ <literal>USING</literal> clause on tables that have a common
+ column name.
+ </para>
+
+ <para>
These changes make MySQL more compliant with standard SQL.
However, they can result in different output columns for some
joins. Also, some queries that appeared to work correctly prior
@@ -28125,6 +28143,10 @@
<manual type="DROP DATABASE"/>
<manual type="CREATE TABLE"/>
<manual type="TRUNCATE TABLE"/>
+ <manual type="replication"/>
+ <manual type="CREATE DATABASE"/>
+ <manual type="ROLLBACK"/>
+ <manual type="binary log"/>
</tags>
<bugs>
@@ -28139,12 +28161,48 @@
<message>
<para>
- The statements <literal>CREATE TABLE</literal>,
- <literal>TRUNCATE TABLE</literal>, <literal>DROP
- DATABASE</literal>, and <literal>CREATE DATABASE</literal> cause
- an implicit commit.
+ Some data definition statements (<literal>CREATE TABLE</literal>
+ where the table was not a temporary table, <literal>TRUNCATE
+ TABLE</literal>, <literal>DROP DATABASE</literal>, and
+ <literal>CREATE DATABASE</literal>) were not being written to
+ the binary log after a <literal>ROLLBACK</literal>. This also
+ caused problems with replication.
</para>
+ <important>
+ <para>
+ As a result of this fix, the folowing statements now cause an
+ implicit commit:
+ <itemizedlist>
+
+ <listitem>
+ <para>
+ <literal>CREATE TABLE</literal>
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>TRUNCATE TABLE</literal>
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>DROP DATABASE</literal>
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>CREATE DATABASE</literal>
+ </para>
+ </listitem>
+
+ </itemizedlist>
+ </para>
+ </important>
+
</message>
</logentry>
@@ -28772,6 +28830,8 @@
<bugs>
<fixes bugid="7115"/>
+ <seealsobug bugid="10975"/>
+ <seealsobug bugid="10605"/>
</bugs>
<versions>
@@ -28783,13 +28843,18 @@
<para>
Using <literal>PREPARE</literal> to prepare a statement that
invoked a stored routine that executed the prepared statement
- caused a <literal>Packets out of order</literal> error the
+ caused a <errortext>Packets out of order error</errortext> the
second time the routine was invoked. This is prevented by
- disabling dynamic SQL within stored routines. (Note: This
- restriction was lifted in 5.0.13 for stored procedures, but not
- stored functions or triggers.)
+ disabling dynamic SQL within stored routines.
</para>
+ <note>
+ <para>
+ This restriction was lifted in 5.0.13 for stored procedures,
+ but not for stored functions or triggers.
+ </para>
+ </note>
+
</message>
</logentry>
@@ -35382,11 +35447,12 @@
</logentry>
- <logentry entrytype="feature">
+ <logentry entrytype="bug">
<tags>
<manual type="InnoDB"/>
<manual type="AUTO_INCREMENT"/>
+ <manual type="ALTER TABLE"/>
</tags>
<bugs>
@@ -35395,18 +35461,18 @@
<versions>
<version ver="4.1.12"/>
+ <version ver="5.0.3"/>
</versions>
<message>
<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> now
- works, and <literal>ALTER TABLE ... AUTO_INCREMENT =
- <replaceable>n</replaceable> </literal> resets the current
- value.
+ Setting the initial <literal>AUTO_INCREMENT</literal> value for
+ an <literal>InnoDB</literal> table using <literal>CREATE TABLE
+ ... AUTO_INCREMENT = <replaceable>n</replaceable> </literal> did
+ not work, and <literal>ALTER TABLE ... AUTO_INCREMENT =
+ <replaceable>n</replaceable> </literal> did not reset the
+ current value.
</para>
</message>
@@ -36279,38 +36345,6 @@
</logentry>
- <logentry entrytype="bug">
-
- <tags>
- <manual type="mysqldump"/>
- <manual type="CREATE DATABASE"/>
- <manual type="transactions"/>
- <manual type="SHOW CREATE DATABASE"/>
- </tags>
-
- <bugs>
- <fixes bugid="7358"/>
- </bugs>
-
- <versions>
- <version ver="5.0.3"/>
- </versions>
-
- <message>
-
- <para>
- Made the MySQL server accept executing <literal>SHOW CREATE
- DATABASE</literal> even if the connection has an open
- transaction or locked tables; refusing it made
- <command>mysqldump --single-transaction</command> sometimes fail
- to print a complete <literal>CREATE DATABASE</literal> statement
- for some dumped databases.
- </para>
-
- </message>
-
- </logentry>
-
<logentry entrytype="feature">
<tags>
@@ -41037,8 +41071,8 @@
</tags>
<bugs>
- <fixes bugid="7142"/>
<fixes bugid="12817"/>
+ <revertsbug bugid="7142"/>
</bugs>
<versions>
@@ -41048,11 +41082,11 @@
<message>
<para>
- Reverted a change introduced in MySQL 4.1.13 to fix a problem of
- <literal>SHOW FIELDS</literal> truncating the
- <literal>TYPE</literal> column to 40 characters. This fix was
- reverted for MySQL 4.1 because it broke existing applications.
- The fix will be made to MySQL 5.0 instead (5.0.13).
+ Reverted a change introduced in MySQL 4.1.13 (<literal>SHOW
+ FIELDS</literal> truncated the <literal>TYPE</literal> column to
+ 40 characters). This fix was reverted for MySQL 4.1 because it
+ broke existing applications. The fix will be made in MySQL 5.0
+ instead (5.0.13).
</para>
</message>
@@ -44809,34 +44843,6 @@
<logentry entrytype="bug">
<tags>
- <manual type="mysql_server_end"/>
- <manual type="mysql_server_init"/>
- </tags>
-
- <bugs>
- <fixes bugid="7344"/>
- </bugs>
-
- <versions>
- <version ver="4.1.12"/>
- </versions>
-
- <message>
-
- <para>
- Additional fix for <literal>mysql_server_init()</literal> and
- <literal>mysql_server_end()</literal> C API functions so that
- stopping and restarting the embedded server will not cause a
- crash.
- </para>
-
- </message>
-
- </logentry>
-
- <logentry entrytype="bug">
-
- <tags>
<manual type="TRADITIONAL"/>
</tags>
@@ -55857,18 +55863,28 @@
</bugs>
<versions>
+ <version ver="4.1.11"/>
<version ver="5.0.4"/>
</versions>
- <message>
+ <message ver="4.1.11">
<para>
- Link with <literal>libsupc++</literal> on Fedora Core 3 to get
- language support functions.
+ A problem with static variables did not allow building the
+ server on Fedora Core 3.
</para>
</message>
+ <message ver="5.0.4">
+
+ <para>
+ Added linking with <literal>libsupc++</literal> on Fedora Core 3
+ to get language support functions.
+ </para>
+
+ </message>
+
</logentry>
<logentry entrytype="bug">
@@ -56998,28 +57014,6 @@
<logentry entrytype="bug">
- <bugs>
- <fixes bugid="7249"/>
- </bugs>
-
- <versions>
- <version ver="5.0.10"/>
- <version ver="4.1.14"/>
- </versions>
-
- <message>
-
- <para>
- The MySQL server had issues with certain combinations of basedir
- and datadir.
- </para>
-
- </message>
-
- </logentry>
-
- <logentry entrytype="bug">
-
<tags>
<manual type="NDB"/>
<manual type="mysql-test-run.pl"/>
@@ -58443,27 +58437,6 @@
<logentry entrytype="bug">
<bugs>
- <fixes bugid="6554"/>
- </bugs>
-
- <versions>
- <version ver="4.1.11"/>
- </versions>
-
- <message>
-
- <para>
- Fixed problems with static variables to allow building on Fedora
- Core 3.
- </para>
-
- </message>
-
- </logentry>
-
- <logentry entrytype="bug">
-
- <bugs>
<fixes bugid="27406"/>
</bugs>
@@ -79038,6 +79011,7 @@
<tags>
<manual type="BLOB"/>
+ <manual type="character sets"/>
<manual type="InnoDB"/>
</tags>
@@ -79048,15 +79022,14 @@
<versions>
<version ver="4.1.11"/>
+ <version ver="5.0.4"/>
</versions>
<message>
<para>
- <literal>InnoDB</literal>: Do not try to space-pad
- <literal>BLOB</literal> columns containing
- <literal>ucs2</literal> characters. This avoids an assertion
- failure that was introduced when fixing Bug #7350.
+ Do not try to space-pad <literal>BLOB</literal> columns
+ containing <literal>ucs2</literal> characters.
</para>
</message>
@@ -80175,32 +80148,6 @@
<logentry entrytype="bug">
<tags>
- <manual type="SHOW FIELDS"/>
- <manual type="TYPE"/>
- </tags>
-
- <bugs>
- <fixes bugid="7142"/>
- </bugs>
-
- <versions>
- <version ver="5.0.13"/>
- </versions>
-
- <message>
-
- <para>
- <literal>SHOW FIELDS</literal> truncated the
- <literal>TYPE</literal> column to 40 characters.
- </para>
-
- </message>
-
- </logentry>
-
- <logentry entrytype="bug">
-
- <tags>
<manual type="BDB"/>
<manual type="double"/>
<manual type="ulonglong"/>
@@ -88104,36 +88051,6 @@
</logentry>
- <logentry entrytype="bug">
-
- <tags>
- <manual type="InnoDB"/>
- <manual type="AUTO_INCREMENT"/>
- <manual type="ALTER"/>
- </tags>
-
- <bugs>
- <fixes bugid="7061"/>
- </bugs>
-
- <versions>
- <version ver="5.0.3"/>
- </versions>
-
- <message>
-
- <para>
- <literal>InnoDB</literal>: Fixed a bug no error message for
- <literal>ALTER</literal> with <literal>InnoDB</literal> and
- <literal>AUTO_INCREMENT</literal> . <literal>InnoDB</literal>
- now supports <literal>ALTER TABLE...AUTO_INCREMENT = x</literal>
- query to set auto increment value for a table.
- </para>
-
- </message>
-
- </logentry>
-
<logentry entrytype="feature">
<tags>
@@ -88431,6 +88348,7 @@
<tags>
<manual type="character sets"/>
+ <manual type="InnoDB"/>
</tags>
<bugs>
@@ -88439,12 +88357,13 @@
<versions>
<version ver="4.1.10"/>
+ <version ver="5.0.3"/>
</versions>
<message>
<para>
- InnoDB: Corrected the handling of trailing spaces in the
+ Corrected the handling of trailing spaces in the
<literal>ucs2</literal> character set.
</para>
@@ -89365,42 +89284,6 @@
<logentry entrytype="bug">
<tags>
- <manual type="replication"/>
- <manual type="CREATE DATABASE"/>
- <manual type="ROLLBACK"/>
- <manual type="binary log"/>
- <manual type="DROP DATABASE"/>
- <manual type="CREATE TABLE"/>
- <manual type="TRUNCATE TABLE"/>
- </tags>
-
- <bugs>
- <fixes bugid="6883"/>
- </bugs>
-
- <versions>
- <version ver="4.1.8"/>
- <version ver="5.0.8"/>
- </versions>
-
- <message>
-
- <para>
- Some data definition statements (<literal>CREATE TABLE</literal>
- where the table was not a temporary table, <literal>TRUNCATE
- TABLE</literal>, <literal>DROP DATABASE</literal>, and
- <literal>CREATE DATABASE</literal>) were not being written to
- the binary log after a <literal>ROLLBACK</literal>. This also
- caused problems with replication.
- </para>
-
- </message>
-
- </logentry>
-
- <logentry entrytype="bug">
-
- <tags>
<manual type="InnoDB"/>
</tags>
@@ -89792,33 +89675,6 @@
</logentry>
- <logentry entrytype="bug">
-
- <tags>
- <manual type="USING"/>
- </tags>
-
- <bugs>
- <fixes bugid="6558"/>
- </bugs>
-
- <versions>
- <version ver="5.0.12"/>
- </versions>
-
- <message>
-
- <para>
- A <quote>Duplicate column name</quote> error no longer occurs
- when selecting from a view defined as <literal>SELECT
- *</literal> from a join that uses a <literal>USING</literal>
- clause on tables that have a common column name.
- </para>
-
- </message>
-
- </logentry>
-
<logentry entrytype="feature">
<tags>
@@ -91756,9 +91612,9 @@
</tags>
<bugs>
- <fixes bugid="7115"/>
<fixes bugid="10975"/>
<fixes bugid="10605"/>
+ <seealsobug bugid="7115"/>
</bugs>
<versions>
@@ -99654,35 +99510,6 @@
</logentry>
- <logentry entrytype="feature">
-
- <tags>
- <manual type="mysqldump"/>
- <manual type="DELAYED"/>
- <manual type="delayed-inserts"/>
- </tags>
-
- <bugs>
- <fixes bugid="7815"/>
- </bugs>
-
- <versions>
- <version ver="5.0.14"/>
- </versions>
-
- <message>
-
- <para>
- Re-enabled the <option>--delayed-inserts</option> option for
- <command>mysqldump</command>, which now checks for each table
- dumped whether its storage engine supports
- <literal>DELAYED</literal> inserts.
- </para>
-
- </message>
-
- </logentry>
-
<logentry entrytype="bug">
<tags>
@@ -105369,35 +105196,6 @@
<logentry entrytype="bug">
<tags>
- <manual type="CHECK TABLE"/>
- <manual type="collation"/>
- </tags>
-
- <bugs>
- <fixes bugid="6505"/>
- </bugs>
-
- <versions>
- <version ver="4.1.12"/>
- </versions>
-
- <message>
-
- <para>
- Fixed a sort order problem with the
- <literal>latin2_croatian_ci</literal> collation. All tables that
- have indexes that use this collation will be treated as crashed.
- After upgrading, for each such table, you must use
- <literal>CHECK TABLE</literal> and possibly repair the table.
- </para>
-
- </message>
-
- </logentry>
-
- <logentry entrytype="bug">
-
- <tags>
<highlight type="cluster"/>
<manual type="UPDATE"/>
</tags>
@@ -105668,6 +105466,12 @@
<logentry entrytype="bug">
+ <tags>
+ <manual type="HAVING"/>
+ <manual type="ORDER BY"/>
+ <manual type="UNSIGNED"/>
+ </tags>
+
<bugs>
<fixes bugid="7425"/>
</bugs>
@@ -105680,9 +105484,10 @@
<message>
<para>
- Ordering by unsigned expression (more complex than a column
+ Ordering by an unsigned expression (more complex than a column
reference) was treating the value as signed, producing
- incorrectly sorted results.
+ incorrectly sorted results. <literal>HAVING</literal> was also
+ treating unsigned columns as signed.
</para>
</message>
@@ -118058,32 +117863,6 @@
</logentry>
- <logentry entrytype="bug">
-
- <tags>
- <manual type="HAVING"/>
- </tags>
-
- <bugs>
- <fixes bugid="7425"/>
- </bugs>
-
- <versions>
- <version ver="4.1.11"/>
- <version ver="5.0.3"/>
- </versions>
-
- <message>
-
- <para>
- <literal>HAVING</literal> was treating unsigned columns as
- signed.
- </para>
-
- </message>
-
- </logentry>
-
<logentry entrytype="feature">
<tags>
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r8339 - trunk/dynamic-docs/changelog | jon | 26 Oct |
