Author: paul
Date: 2006-09-14 05:30:50 +0200 (Thu, 14 Sep 2006)
New Revision: 3350
Log:
Document bugfixes:
Bug#19874
Bug#20402
Bug#20791
Modified:
trunk/refman-5.1/news-5.1.xml
Modified: trunk/refman-5.1/news-5.1.xml
===================================================================
--- trunk/refman-5.1/news-5.1.xml 2006-09-14 03:05:54 UTC (rev 3349)
+++ trunk/refman-5.1/news-5.1.xml 2006-09-14 03:30:50 UTC (rev 3350)
Changed blocks: 3, Lines Added: 19, Lines Deleted: 1; 1676 bytes
@@ -684,6 +684,15 @@
<listitem>
<para>
+ Identifiers with embedded escape characters were not handled
+ correctly by some <literal>SHOW</literal> statements due to
+ some old code that was doing some extra unescaping. (Bug
+ #19874)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
<literal>INNODB</literal> was slow with more than 100,000
<filename>.idb</filename> files. (Bug #21112)
</para>
@@ -848,6 +857,13 @@
<listitem>
<para>
+ Some user-level level errors were being written to the
+ server's error log, which is for server errors. (Bug #20402)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
to the client could have an empty column name. When using
tables created under MySQL 4.1 with a 5.0 server, if the
tables contained <literal>VARCHAR</literal> columns, for some
@@ -3335,7 +3351,9 @@
were corrected: Possible uninitialized data in a string
comparison (Bug #20783); memory corruption in replication
slaves when switching databases (Bug #19022); syscall write
- parameter pointing to uninitialized byte (Bug #20579).
+ parameter pointing to uninitialized byte (Bug #20579);
+ uninitialized doublewrite memory in <literal>InnoDB</literal>
+ (Bug#20791).
</para>
</listitem>
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r3350 - trunk/refman-5.1 | paul | 14 Sep |
