Author: paul
Date: 2006-07-13 06:29:10 +0200 (Thu, 13 Jul 2006)
New Revision: 2722
Log:
r12145@frost: paul | 2006-07-12 23:25:11 -0500
Document bugfixes:
Bug#10166
Bug#11824
Bug#16674
Bug#19392
Bug#19773
Bug#20579
Modified:
trunk/make.d/xml-html-chapter
trunk/mysqltest/mysqltest.xml
trunk/refman-common/news-4.1.xml
trunk/refman-common/news-5.0.xml
trunk/refman-common/news-5.1.xml
trunk/tools/xmlformat.conf
Property changes on: trunk
___________________________________________________________________
Name: svk:merge
- 4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:11327
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:12144
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:8441
+ 4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:11327
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:12145
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:8441
Modified: trunk/make.d/xml-html-chapter
===================================================================
--- trunk/make.d/xml-html-chapter 2006-07-13 04:28:55 UTC (rev 2721)
+++ trunk/make.d/xml-html-chapter 2006-07-13 04:29:10 UTC (rev 2722)
Changed blocks: 1, Lines Added: 6, Lines Deleted: 10; 920 bytes
@@ -4,20 +4,16 @@
# Use html-section driver file, but set chunk.section.depth to 0,
# causes chunking at the chapter level.
-%.html-chapter: %.html-chapter.d
- touch $@
-
-.PRECIOUS: %.html-chapter.d
-
-%.html-chapter.d: %-prepped.xml $(MYSQL_HTML_SECTION_XSL_DEPS)
- -$(RM) -r $@/
- mkdir $@/
+%.html-chapter: %-prepped.xml $(MYSQL_HTML_SECTION_XSL_DEPS)
+ -$(RM) -r $@/ $@-tmp/
+ mkdir $@-tmp/
$(XSLTPROC) \
--stringparam l10n.gentext.default.language $(DOC_LANG) \
--param chunk.section.depth 0 \
- --output $@/ \
+ --output $@-tmp/ \
$(MYSQL_HTML_SECTION_XSL) \
$<
+ mv $@-tmp/ $@/
clean::
- $(RM) -r *.html-chapter *.html-chapter.d
+ $(RM) -r *.html-chapter *.html-chapter-tmp
Modified: trunk/mysqltest/mysqltest.xml
===================================================================
--- trunk/mysqltest/mysqltest.xml 2006-07-13 04:28:55 UTC (rev 2721)
+++ trunk/mysqltest/mysqltest.xml 2006-07-13 04:29:10 UTC (rev 2722)
Changed blocks: 1, Lines Added: 14, Lines Deleted: 7; 1505 bytes
@@ -27,21 +27,28 @@
</abstract>
- <xi:include href="legalnotice.en.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
+ <xi:include href="legalnotice.en.xml"
+ xmlns:xi="http://www.w3.org/2001/XInclude"/>
</bookinfo>
- <xi:include href="preface.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
+ <xi:include href="preface.xml"
+ xmlns:xi="http://www.w3.org/2001/XInclude"/>
- <xi:include href="introduction.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
+ <xi:include href="introduction.xml"
+ xmlns:xi="http://www.w3.org/2001/XInclude"/>
- <xi:include href="components.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
+ <xi:include href="components.xml"
+ xmlns:xi="http://www.w3.org/2001/XInclude"/>
- <xi:include href="tutorial.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
+ <xi:include href="tutorial.xml"
+ xmlns:xi="http://www.w3.org/2001/XInclude"/>
- <xi:include href="programs.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
+ <xi:include href="programs.xml"
+ xmlns:xi="http://www.w3.org/2001/XInclude"/>
- <xi:include href="command-reference.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
+ <xi:include href="command-reference.xml"
+ xmlns:xi="http://www.w3.org/2001/XInclude"/>
<index/>
Modified: trunk/refman-common/news-4.1.xml
===================================================================
--- trunk/refman-common/news-4.1.xml 2006-07-13 04:28:55 UTC (rev 2721)
+++ trunk/refman-common/news-4.1.xml 2006-07-13 04:29:10 UTC (rev 2722)
Changed blocks: 1, Lines Added: 30, Lines Deleted: 0; 1657 bytes
@@ -223,6 +223,36 @@
<listitem>
<para>
+ The length of the pattern string prefix for
+ <literal>LIKE</literal> operations was calculated incorrectly
+ for multi-byte character sets. As a result, the the scanned
+ range was wider than necessary if the prefix contained any
+ multi-byte characters. (Bug #16674)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ For very complex <literal>SELECT</literal> statements could
+ create temporary tables that were too big, but for which the
+ temporary files did not get removed, causing subsequent
+ queries to fail. (Bug #11824)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Invalid arguments to <literal>DATE_FORMAT()</literal> caused a
+ server crash.
+ (<ulink url="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2006-3469">CVE-2006-3469</ulink>,
+ Bug #20729) Thanks to Jean-David Maillefer for discovering and
+ reporting this problem to the Debian project and to Christian
+ Hammers from the Debian Team for notifying us of it.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
Using <literal>SELECT</literal> and a table join while running
a concurrent <literal>INSERT</literal> operation would join
incorrect rows. (Bug #14400)
Modified: trunk/refman-common/news-5.0.xml
===================================================================
--- trunk/refman-common/news-5.0.xml 2006-07-13 04:28:55 UTC (rev 2721)
+++ trunk/refman-common/news-5.0.xml 2006-07-13 04:29:10 UTC (rev 2722)
Changed blocks: 1, Lines Added: 29, Lines Deleted: 0; 1551 bytes
@@ -312,6 +312,35 @@
<listitem>
<para>
+ The length of the pattern string prefix for
+ <literal>LIKE</literal> operations was calculated incorrectly
+ for multi-byte character sets. As a result, the the scanned
+ range was wider than necessary if the prefix contained any
+ multi-byte characters, and rows could be missing from the
+ result set. (Bug #16674)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ For very complex <literal>SELECT</literal> statements could
+ create temporary tables that were too big, but for which the
+ temporary files did not get removed, causing subsequent
+ queries to fail. (Bug #11824)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ For spatial data types, the server formerly returned these as
+ <literal>VARSTRING</literal> values with a binary collation.
+ Now the server returns spatial values as
+ <literal>BLOB</literal> values. (Bug #10166)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
Using <literal>SELECT</literal> and a table join while running
a concurrent <literal>INSERT</literal> operation would join
incorrect rows. (Bug #14400)
Modified: trunk/refman-common/news-5.1.xml
===================================================================
--- trunk/refman-common/news-5.1.xml 2006-07-13 04:28:55 UTC (rev 2721)
+++ trunk/refman-common/news-5.1.xml 2006-07-13 04:29:10 UTC (rev 2722)
Changed blocks: 3, Lines Added: 46, Lines Deleted: 2; 2524 bytes
@@ -314,6 +314,49 @@
<listitem>
<para>
+ The length of the pattern string prefix for
+ <literal>LIKE</literal> operations was calculated incorrectly
+ for multi-byte character sets. As a result, the the scanned
+ range was wider than necessary if the prefix contained any
+ multi-byte characters, and rows could be missing from the
+ result set. (Bug #16674)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ For very complex <literal>SELECT</literal> statements could
+ create temporary tables that were too big, but for which the
+ temporary files did not get removed, causing subsequent
+ queries to fail. (Bug #11824)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Multiple-table updates with <literal>FEDERATED</literal>
+ tables could cause a server crash. (Bug #19773)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Renaming a database to itself caused a server crash. (Bug
+ #19392)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ For spatial data types, the server formerly returned these as
+ <literal>VARSTRING</literal> values with a binary collation.
+ Now the server returns spatial values as
+ <literal>BLOB</literal> values. (Bug #10166)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
Using tables from MySQL 4.x in MySQL 5.x, in particular those
with <literal>VARCHAR</literal> fields and using
<literal>INSERT DELAYED</literal> to update data in the table
@@ -511,7 +554,7 @@
could cause errors or crash the server. (Bug #20583)
</para>
</listitem>
-
+
<listitem>
<para>
<literal>NDB Cluster</literal>: Trying to create or drop a
@@ -1263,7 +1306,8 @@
<para>
For <command>mysqld</command>, Valgrind revealed problems that
were corrected: Memory corruption in replication slaves when
- switching databases (Bug #19022).
+ switching databases (Bug #19022); syscall write parameter
+ pointing to uninitialized byte (Bug #20579).
</para>
</listitem>
Modified: trunk/tools/xmlformat.conf
===================================================================
--- trunk/tools/xmlformat.conf 2006-07-13 04:28:55 UTC (rev 2721)
+++ trunk/tools/xmlformat.conf 2006-07-13 04:29:10 UTC (rev 2722)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 432 bytes
@@ -43,7 +43,7 @@
entry-break 1
exit-break 1
-para remark textobject releaseinfo
+para remark textobject releaseinfo term
format block
entry-break 1
exit-break 1
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r2722 - in trunk: . make.d mysqltest refman-common tools | paul | 13 Jul |
