Author: paul
Date: 2005-10-20 22:44:54 +0200 (Thu, 20 Oct 2005)
New Revision: 120
Log:
r126@kite-hub: paul | 2005-10-20 11:32:48 -0500
Add missing <listitem> tags, reformat.
Modified:
trunk/
trunk/refman-common/news-5.0.xml
Property changes on: trunk
___________________________________________________________________
Name: svk:merge
- b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:2935
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:87
+ b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:2935
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:126
Modified: trunk/refman-common/news-5.0.xml
===================================================================
--- trunk/refman-common/news-5.0.xml 2005-10-20 19:55:45 UTC (rev 119)
+++ trunk/refman-common/news-5.0.xml 2005-10-20 20:44:54 UTC (rev 120)
@@ -162,17 +162,17 @@
For a full list of changes, please refer to the changelog sections
for each individual 5.0.x release.
</para>
-
+
<section id="news-5-0-16">
-
+
<title id="title-news-5-0-16">&title-news-5-0-16;</title>
-
+
<para>
Functionality added or changed:
</para>
-
+
<itemizedlist>
-
+
<listitem>
<para>
MySQL 5.0 now supports character set conversion for seven
@@ -181,52 +181,59 @@
<literal>0xF9D6</literal>, <literal>0xF9D7</literal>,
<literal>0xF9D8</literal>, <literal>0xF9D9</literal>,
<literal>0xF9DA</literal>, <literal>0xF9DB</literal>, and
- <literal>0xF9DC</literal>. <emphasis
- role="bold">Note</emphasis>: If you move data containing
- these additional characters to an older MySQL installation
- which does not support them, you may encounter errors. (Bug
- #12476)
+ <literal>0xF9DC</literal>.
+ <emphasis role="bold">Note</emphasis>: If you move data
+ containing these additional characters to an older MySQL
+ installation which does not support them, you may encounter
+ errors. (Bug #12476)
</para>
</listitem>
-
+
</itemizedlist>
-
+
<para>
Bugs fixed:
</para>
-
+
<itemizedlist>
-
- <para>
- <command>mysqladmin</command> and <command>mysqldump</command>
- would hang on SCO OpenServer. (Bug #13238)
- </para>
-
- <para>
- <literal>RESET MASTER</literal> failed to delete logfiles on
- Windows. (Bug #13377)
- </para>
-
- <para>
- Where one stored procedure called another stored procedure: If
- the second stored procedure generated an exception, the
- exception was not caught by the calling stored procedure. For
- example, if stored procedure <literal>A</literal> used an
- <literal>EXIT</literal> statement to handle an exception,
- subsequent statements in <literal>A</literal> would be executed
- regardless when <literal>A</literal> was called by another
- stored procedure <literal>B</literal>, even if an exception that
- should have been handled by the <literal>EXIT</literal> was
- generated in <literal>A</literal>. (Bug #7049)
- </para>
-
+
<listitem>
<para>
+ <command>mysqladmin</command> and <command>mysqldump</command>
+ would hang on SCO OpenServer. (Bug #13238)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>RESET MASTER</literal> failed to delete log files on
+ Windows. (Bug #13377)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Where one stored procedure called another stored procedure: If
+ the second stored procedure generated an exception, the
+ exception was not caught by the calling stored procedure. For
+ example, if stored procedure <literal>A</literal> used an
+ <literal>EXIT</literal> statement to handle an exception,
+ subsequent statements in <literal>A</literal> would be
+ executed regardless when <literal>A</literal> was called by
+ another stored procedure <literal>B</literal>, even if an
+ exception that should have been handled by the
+ <literal>EXIT</literal> was generated in <literal>A</literal>.
+ (Bug #7049)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
Trying to create a stored routine with no database selected
would crash the server. (Bug #13514, Bug #13587)
</para>
</listitem>
-
+
<listitem>
<para>
Specifying <option>--default-character-set=cp-932</option> for
@@ -235,7 +242,7 @@
syntax error. (Bug #13487)
</para>
</listitem>
-
+
<listitem>
<para>
Trying to compile the server using the
@@ -243,12 +250,11 @@
fail. (Bug #12991)
</para>
</listitem>
-
+
</itemizedlist>
-
+
</section>
-
-
+
<section id="news-5-0-15">
<title id="title-news-5-0-15">&title-news-5-0-15;</title>
@@ -274,7 +280,7 @@
<xref linkend="upgrading-from-4-1"/>.
</para>
</listitem>
-
+
<listitem>
<para>
<literal>NDBCluster</literal>: The <command>perror</command>
@@ -284,12 +290,12 @@
Cluster error codes. (Bug #13740)
</para>
</listitem>
-
+
<listitem>
<para>
When executing single-table <literal>UPDATE</literal> or
<literal>DELETE</literal> queries containing an <literal>ORDER
- BY ... LIMIT <replaceable>N</replaceable></literal> clause,
+ BY ... LIMIT <replaceable>N</replaceable></literal> clause,
but not having any <literal>WHERE</literal> clause, MySQL can
now take advantage of an index to read the first
<replaceable>N</replaceable> rows in the ordering specified in
@@ -8967,7 +8973,7 @@
<para>
Fixed that <command>mysqlbinlog
--read-from-remote-server</command> sometimes couldn't accept
- two binary logfiles on the command line. (Bug #4507)
+ two binary log files on the command line. (Bug #4507)
</para>
</listitem>
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r120 - in trunk: . refman-common | paul | 20 Oct |
