List:Internals« Previous MessageNext Message »
From:jstephens Date:October 20 2005 8:38am
Subject:svn commit - mysqldoc@docsrva: r118 - trunk/refman-common
View as plain text  
Author: jstephens
Date: 2005-10-20 10:37:59 +0200 (Thu, 20 Oct 2005)
New Revision: 118

Log:

refman-common/news-connector-net.xml - Documented fix for Bug#13753

refman-common/news-4.1.xml 
  - Documented fixes for Bug#13535, Bug#13487, Bug#13740, Bug#12476, Bug#13377,
    Bug#13238
  
refman-common/news-5.0.xml
  - Documented fixes for Bug#12991, Bug#13487, Bug#13514/Bug#13587, Bug#13740,
    Bug#7049, Bug#12476, Bug#13377, Bug#13238
  - Added new news-5-0-16 section

refman-common/titles.en.ent - Added new section title (for 5.0.16 changelog)




Modified:
   trunk/refman-common/news-4.1.xml
   trunk/refman-common/news-5.0.xml
   trunk/refman-common/news-connector-net.xml
   trunk/refman-common/titles.en.ent

Modified: trunk/refman-common/news-4.1.xml
===================================================================
--- trunk/refman-common/news-4.1.xml	2005-10-20 03:28:50 UTC (rev 117)
+++ trunk/refman-common/news-4.1.xml	2005-10-20 08:37:59 UTC (rev 118)
@@ -166,9 +166,35 @@
     </para>
 
     <itemizedlist>
+  
+      <listitem>
+        <para>
+          MySQL 4.1 now supports character set conversion for seven
+          additional <literal>cp950</literal> characters into the
+          <literal>big5</literal> character set:
+          <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)  
+        </para>
+      </listitem>
       
       <listitem>
         <para>
+          <literal>NDBCluster</literal>: The <command>perror</command>
+          utility included with the <literal>MySQL-Server</literal> RPM
+          now provides support for the <option>--ndb</option> option,
+          and so can be used to obtain error message text for MySQL
+          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,
@@ -207,6 +233,30 @@
     </remark>
 
     <itemizedlist>
+      
+      <para>
+        <command>mysqladmin</command> and <command>mysqldump</command>
+        would hang on SCO OpenServer. (Bug #13238)
+      </para>
+      
+      <listitem>
+        <para>
+          Specifying <option>--default-character-set=cp-932</option> for
+          <command>mysqld</command> would cause SQL scripts containing
+          comments written using that character set to fail with a
+          syntax error. (Bug #13487)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          Given a column <replaceable>col_name</replaceable> defined as
+          <literal>NOT NULL</literal>, a <literal>SELECT ... FROM ...
+            WHERE <replaceable>col_name</replaceable> IS NULL</literal> 
+          query following <literal>SHOW TABLE STATUS</literal> would
+          erroneously return a non-empty result. (Bug #13535)
+        </para>
+      </listitem>
 
       <listitem>
         <para>

Modified: trunk/refman-common/news-5.0.xml
===================================================================
--- trunk/refman-common/news-5.0.xml	2005-10-20 03:28:50 UTC (rev 117)
+++ trunk/refman-common/news-5.0.xml	2005-10-20 08:37:59 UTC (rev 118)
@@ -162,7 +162,93 @@
     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
+          additional <literal>cp950</literal> characters into the
+          <literal>big5</literal> character set:
+          <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)  
+        </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>
+          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
+          <command>mysqld</command> would cause SQL scripts containing
+          comments written using that character set to fail with a
+          syntax error. (Bug #13487)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          Trying to compile the server using the
+          <option>--without-geometry</option> option caused the build to
+          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>
@@ -191,6 +277,16 @@
       
       <listitem>
         <para>
+          <literal>NDBCluster</literal>: The <command>perror</command>
+          utility included with the <literal>MySQL-Server</literal> RPM
+          now provides support for the <option>--ndb</option> option,
+          and so can be used to obtain error message text for MySQL
+          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,

Modified: trunk/refman-common/news-connector-net.xml
===================================================================
--- trunk/refman-common/news-connector-net.xml	2005-10-20 03:28:50 UTC (rev 117)
+++ trunk/refman-common/news-connector-net.xml	2005-10-20 08:37:59 UTC (rev 118)
@@ -43,6 +43,15 @@
     <title>Version 1.0.7</title>
 
     <itemizedlist>
+      
+      <listitem>
+        <para>
+          Calling a stored procedure where a parameter contained special
+          characters (such as <literal>'@'</literal>) would produce an
+          exception. Note that <literal>ANSI_QUOTES</literal> had to be
+          enabled to make this possible. (Bug #13753)
+        </para>
+      </listitem>
 
       <listitem>
         <para>
@@ -53,8 +62,8 @@
 
       <listitem>
         <para>
-          <literal>Ping()</literal> method did not update
-          <literal>State</literal> property of
+          The <literal>Ping()</literal> method did not update
+          the <literal>State</literal> property of the
           <literal>Connection</literal> object. (Bug #13658)
         </para>
       </listitem>
@@ -71,15 +80,15 @@
 
       <listitem>
         <para>
-          <literal>nant</literal> build sequence had problems. (Bug
+          The <literal>nant</literal> build sequence had problems. (Bug
           #12978)
         </para>
       </listitem>
 
       <listitem>
         <para>
-          Serializing a parameter fails if first value passed in
-          <literal>NULL</literal>. (Bug #13276)
+          Serializing a parameter failed if the first value passed in
+          was <literal>NULL</literal>. (Bug #13276)
         </para>
       </listitem>
 
@@ -92,7 +101,7 @@
 
       <listitem>
         <para>
-          &connector_net; 1.0.5 installer would not install alongside
+          The &connector_net; 1.0.5 installer would not install alongside
           &connector_net; 1.0.4. (Bug #12835)
         </para>
       </listitem>
@@ -152,71 +161,67 @@
 
       <listitem>
         <para>
-          Call to stored procedure causes exception if stored procedure
-          has no parameters. (Bug #11542)
+          A call to a stored procedure caused an exception if the stored
+          procedure had no parameters. (Bug #11542)
         </para>
       </listitem>
 
       <listitem>
         <para>
-          Certain malformed queries will trigger a "Connection must be
-          valid and open" error message. (Bug #11490)
+          Certain malformed queries would trigger a <literal>Connection
+            must be valid and open</literal> error message. (Bug #11490)
         </para>
       </listitem>
 
       <listitem>
         <para>
-          Fixed a bug where the <literal>MySqlCommandBuilder</literal>
-          class could not handle queries that references tables in a
-          database other than the default database. (Bug #8382)
+          The <literal>MySqlCommandBuilder</literal> class could not
+          handle queries that referenced tables in a database other than
+          the default database. (Bug #8382)
         </para>
       </listitem>
 
       <listitem>
         <para>
-          Fixed a bug where &connector_net; could not work properly with
-          certain regional settings. (WL#8228)
+          &connector_net; could not work properly with certain regional
+          settings. (WL#8228)
         </para>
       </listitem>
 
       <listitem>
         <para>
-          Fixed an exception when trying to use a stored procedure when
-          Connection.Database is not populated. (Bug #11450)
+          Trying to use a stored procedure when
+          <literal>Connection.Database</literal> was not populated
+          generated an exception. (Bug #11450)
         </para>
       </listitem>
 
       <listitem>
         <para>
-          Fixed an exception when trying to read a
-          <literal>TIMESTAMP</literal> column. (Bug #7951)
+          Trying to read a <literal>TIMESTAMP</literal> column generated
+          an exception. (Bug #7951)
         </para>
       </listitem>
 
       <listitem>
         <para>
-          Fixed error where parameters not recognised when separated by
-          linefeeds.
-          (<ulink url="http://bugs.mysql.com/bug.php?id=9722">Bug
-          #9722</ulink>)
+          Parameters were not recognised when they were separated by
+          linefeeds. (Bug #9722)
         </para>
       </listitem>
 
       <listitem>
         <para>
-          Fixed error when MySqlConnection.clone is called and a
+          Calling <literal>MySqlConnection.clone</literal> when a
           connection string had not yet been set on the original
-          connection.
-          (<ulink url="http://bugs.mysql.com/bug.php?id=10281">Bug
-          #10281</ulink>)
+          connection would generate an error. (Bug #10281)
         </para>
       </listitem>
 
       <listitem>
         <para>
-          Added support to call a stored function from Connector/NET.
-          (<ulink url="http://bugs.mysql.com/bug.php?id=10644">Bug
-          #10644</ulink>)
+          Added support to call a stored function from &connector_net;.
+          (Bug #10644)
         </para>
       </listitem>
 
@@ -229,9 +234,9 @@
 
       <listitem>
         <para>
-          <literal>ConnectionString</literal> property could not be set
-          when <literal>MySqlConnection</literal> object added with
-          designer. (Bug #12551, Bug #8724)
+          The <literal>ConnectionString</literal> property could not be
+          set when a <literal>MySqlConnection</literal> object was added
+          with the designer. (Bug #12551, Bug #8724)
         </para>
       </listitem>
 

Modified: trunk/refman-common/titles.en.ent
===================================================================
--- trunk/refman-common/titles.en.ent	2005-10-20 03:28:50 UTC (rev 117)
+++ trunk/refman-common/titles.en.ent	2005-10-20 08:37:59 UTC (rev 118)
@@ -1166,6 +1166,7 @@
 <!ENTITY title-news-5-0-13 "Changes in release 5.0.13 (22 Sept 2005: Release Candidate)">
 <!ENTITY title-news-5-0-14 "Changes in release 5.0.14 (Not yet released)">
 <!ENTITY title-news-5-0-15 "Changes in release 5.0.15 (Not yet released)">
+<!ENTITY title-news-5-0-16 "Changes in release 5.0.16 (Not yet released)">
 <!ENTITY title-news-5-0-2 "Changes in release 5.0.2 (01 Dec 2004)">
 <!ENTITY title-news-5-0-3 "Changes in release 5.0.3 (23 Mar 2005: Beta)">
 <!ENTITY title-news-5-0-4 "Changes in release 5.0.4 (16 Apr 2005)">

Thread
svn commit - mysqldoc@docsrva: r118 - trunk/refman-commonjstephens20 Oct