bk commit - mysqldoc@docsrva tree (paul:1.3512)

[paul]

Below is the list of changes that have just been committed into a local
mysqldoc repository of paul. When paul does a push these changes will
be propagated to the main repository and, within 24 hours after the
push, to the public repository.
For information on how to access the public repository
see http://www.mysql.com/doc/I/n/Installing_source_tree.html

ChangeSet
  1.3512 05/09/08 15:36:34 paul@stripped +4 -0
  news-5.0.xml:
    Move changelog entry from 5.0.12 to 5.0.13.
  news-5.0.xml, news-4.1.xml:
    Document bugfix. (Bug #12829)
  news-5.0.xml:
    Document bugfix. (Bug #12973)
  news-5.1.xml, news-5.0.xml:
    Document bugfix. (Bug #12084)
  titles.en.ent:
    New section entity.
  news-5.0.xml:
    Document bugfix. (Bug #11815)
    Document bugfix. (Bug #12849)
    Document bugfix. (Bug #12977)

  refman-common/news-5.0.xml
    1.156 05/09/08 15:33:20 paul@stripped +8 -8
    Move changelog entry from 5.0.12 to 5.0.13.

  refman-common/news-5.0.xml
    1.155 05/09/08 15:29:20 paul@stripped +9 -0
    Document bugfix. (Bug #12829)

  refman-common/news-4.1.xml
    1.84 05/09/08 15:29:20 paul@stripped +9 -0
    Document bugfix. (Bug #12829)

  refman-common/news-5.0.xml
    1.154 05/09/08 15:25:12 paul@stripped +9 -0
    Document bugfix. (Bug #12973)

  refman-common/news-5.1.xml
    1.11 05/09/08 15:22:32 paul@stripped +39 -0
    Document bugfix. (Bug #12084)

  refman-common/news-5.0.xml
    1.153 05/09/08 15:22:32 paul@stripped +9 -0
    Document bugfix. (Bug #12084)

  refman-common/titles.en.ent
    1.35 05/09/08 15:18:30 paul@stripped +1 -0
    New section entity.

  refman-common/news-5.0.xml
    1.152 05/09/08 15:04:16 paul@stripped +8 -0
    Document bugfix. (Bug #11815)

  refman-common/news-5.0.xml
    1.151 05/09/08 14:53:48 paul@stripped +9 -0
    Document bugfix. (Bug #12849)

  refman-common/news-5.0.xml
    1.150 05/09/08 14:40:32 paul@stripped +7 -0
    Document bugfix. (Bug #12977)

# This is a BitKeeper patch.  What follows are the unified diffs for the
# set of deltas contained in the patch.  The rest of the patch, the part
# that BitKeeper cares about, is below these diffs.
# User:	paul
# Host:	kite-hub.kitebird.com
# Root:	/src/extern/MySQL/bk/mysqldoc

--- 1.83/refman-common/news-4.1.xml	2005-09-08 12:08:45 -05:00
+++ 1.84/refman-common/news-4.1.xml	2005-09-08 15:29:20 -05:00
@@ -180,6 +180,15 @@
 
       <listitem>
         <para>
+          After changing the character set with <literal>SET CHARACTER
+          SET</literal>, the result of the
+          <literal>GROUP_CONCAT()</literal> function was not converted
+          to the proper character set. (Bug #12829)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
           <command>myisampack</command> did not properly pack
           <literal>BLOB</literal> values larger than
           2<superscript>24</superscript> bytes. (Bug #4214)

--- 1.149/refman-common/news-5.0.xml	2005-09-08 14:14:37 -05:00
+++ 1.156/refman-common/news-5.0.xml	2005-09-08 15:33:20 -05:00
@@ -223,6 +223,65 @@
 
       <listitem>
         <para>
+          Queries with subqueries, where the inner subquery uses the
+          <literal>range</literal> or
<literal>index_merge</literal>
+          access method, could return incorrect results. (Bug #12720)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          After changing the character set with <literal>SET CHARACTER
+          SET</literal>, the result of the
+          <literal>GROUP_CONCAT()</literal> function was not converted
+          to the proper character set. (Bug #12829)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          A bug introduced in MySQL 5.0.12 caused <literal>SHOW TABLE
+          STATUS</literal> to display an
+          <literal>Auto_increment</literal> value of 0 for
+          <literal>InnoDB</literal> tables. (Bug #12973)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          Foreign keys were not properly enforced in
+          <literal>TEMPORARY</literal> tables. Foreign keys now are
+          disallowed in <literal>TEMPORARY</literal> tables. (Bug
+          #12084)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          Replication of <literal>LOAD DATA INFILE</literal> failed
+          between systems that use different pathname syntax (such as
+          delimiter characters). (Bug #11815)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          Within a stored procedure, a server crash was caused by
+          assigning to a <literal>VARCHAR INOUT</literal> parameter the
+          value of an expression that included the variable itself. (For
+          example, <literal>SET c = c</literal>.) (Bug #12849)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          <literal>SELECT ... JOIN ... ON ... JOIN ... USING</literal>
+          caused a server crash. (Bug #12977)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
           Using <literal>GROUP BY</literal> when selecting from a view
           in some cases could cause incorrect results to be returned.
           (Bug #12922)
@@ -708,14 +767,6 @@
           occurred, <command>ndbd</command> exited without printing a
           message about the condition to the error log. Now the message
           is written. (Bug #12716)
-        </para>
-      </listitem>
-
-      <listitem>
-        <para>
-          Queries with subqueries, where the inner subquery uses the
-          <literal>range</literal> or
<literal>index_merge</literal>
-          access method, could return incorrect results. (Bug #12720)
         </para>
       </listitem>
 

--- 1.10/refman-common/news-5.1.xml	2005-09-06 16:15:59 -05:00
+++ 1.11/refman-common/news-5.1.xml	2005-09-08 15:22:32 -05:00
@@ -29,6 +29,45 @@
     for each individual 5.1.x release.
   </para>
 
+  <section id="news-5-1-2">
+
+    <title id="title-news-5-1-2">&title-news-5-1-2;</title>
+
+    <remark role="note">
+      References to bug numbers should be written after the sentence
+      describing the bugfix, like this: This sentence describes the fix.
+      (Bug #nnnn) It is not necessary to to state that the bug was
+      fixed, since "Bugs fixed" already implies this. Use the past tense
+      in describing the bug.
+    </remark>
+
+    <para>
+      Functionality added or changed:
+    </para>
+
+    <remark>
+      ADD AN ITEMIZED LIST WHEN WE HAVE SOME ITEMS THAT GO HERE
+    </remark>
+
+    <para>
+      Bugs fixed:
+    </para>
+
+    <itemizedlist>
+
+      <listitem>
+        <para>
+          Foreign keys were not properly enforced in
+          <literal>TEMPORARY</literal> tables. Foreign keys now are
+          disallowed in <literal>TEMPORARY</literal> tables. (Bug
+          #12084)
+        </para>
+      </listitem>
+
+    </itemizedlist>
+
+  </section>
+
   <section id="news-5-1-1">
 
     <title id="title-news-5-1-1">&title-news-5-1-1;</title>

--- 1.34/refman-common/titles.en.ent	2005-09-08 11:35:11 -05:00
+++ 1.35/refman-common/titles.en.ent	2005-09-08 15:18:30 -05:00
@@ -1127,6 +1127,7 @@
 <!ENTITY title-news-5-0-9 "Changes in release 5.0.9 (15 July 2005)">
 <!ENTITY title-news-5-0-x "Changes in release 5.0.x (Development)">
 <!ENTITY title-news-5-1-1 "Changes in release 5.1.1 (Not yet released)">
+<!ENTITY title-news-5-1-2 "Changes in release 5.1.2 (Not yet released)">
 <!ENTITY title-news-5-1-x "Changes in release 5.1.x (Development)">
 <!ENTITY title-no-matching-rows "Solving Problems with No Matching Rows">
 <!ENTITY title-nocursor "What Causes <literal>Cursor not found</literal>
Errors?">