bk commit - mysqldoc@docsrva tree (Mike.Hillyer:1.3297)

[mhillyer]

Below is the list of changes that have just been committed into a local
mysqldoc repository of root. When root 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.3297 05/08/15 22:17:31 Mike.Hillyer@stripped +3 -0
  Merge bk://mysqldoc@stripped
  into www.openwin.org:/home/mysqldoc/mysqldoc

  refman-common/news-5.0.xml
    1.54 05/08/15 22:17:30 Mike.Hillyer@stripped +0 -0
    Auto merged

  refman-common/news-4.1.xml
    1.37 05/08/15 22:17:30 Mike.Hillyer@stripped +0 -0
    Auto merged

  refman-common/news-4.0.xml
    1.21 05/08/15 22:17:30 Mike.Hillyer@stripped +0 -0
    Auto merged

# 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:	Mike.Hillyer
# Host:	www.openwin.org
# Root:	/home/mysqldoc/mysqldoc/RESYNC

--- 1.20/refman-common/news-4.0.xml	2005-08-15 20:15:36 -06:00
+++ 1.21/refman-common/news-4.0.xml	2005-08-15 22:17:30 -06:00
@@ -165,6 +165,15 @@
 
       <listitem>
         <para>
+          Query cache is switched off if a thread (connection) has
+          tables locked. This prevents invalid results where the locking
+          thread inserts values between a second thread connecting and
+          selecting from the table. (Bug #12385)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
           For PKG installs on Mac OS X, the preinstallation and
           postinstallation scripts were being run only for new
           installations and not for upgrade installations, resulting in

--- 1.36/refman-common/news-4.1.xml	2005-08-15 20:15:36 -06:00
+++ 1.37/refman-common/news-4.1.xml	2005-08-15 22:17:30 -06:00
@@ -228,6 +228,15 @@
         </para>
       </listitem>
 
+      <listitem>
+        <para>
+          Query cache is switched off if a thread (connection) has
+          tables locked. This prevents invalid results where the locking
+          thread inserts values between a second thread connecting and
+          selecting from the table. (Bug #12385)
+        </para>
+      </listitem>
+
     </itemizedlist>
 
     <para>
@@ -238,6 +247,14 @@
      describe the issue that was fixed. Use past tense. -->
 
     <itemizedlist>
+
+      <listitem>
+        <para>
+          Concatenating
+          <literal>USER()</literal>/<literal>DATEBASE()</literal>
with a
+          column produces invalid results. (Bug #12351)
+        </para>
+      </listitem>
 
       <listitem>
         <para>

--- 1.53/refman-common/news-5.0.xml	2005-08-15 20:15:36 -06:00
+++ 1.54/refman-common/news-5.0.xml	2005-08-15 22:17:30 -06:00
@@ -221,6 +221,15 @@
         </para>
       </listitem>
 
+      <listitem>
+        <para>
+          Query cache is switched off if a thread (connection) has
+          tables locked. This prevents invalid results where the locking
+          thread inserts values between a second thread connecting and
+          selecting from the table. (Bug #12385)
+        </para>
+      </listitem>
+
     </itemizedlist>
 
     <para>
@@ -228,6 +237,37 @@
     </para>
 
     <itemizedlist>
+
+      <listitem>
+        <para>
+          <literal>XA</literal> allowed two active transactions to be
+          started with the same XID. (Bug #12162)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          Concatenating
+          <literal>USER()</literal>/<literal>DATEBASE()</literal>
with a
+          column produces invalid results. (Bug #12351)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          Creating a view that included the
+          <literal>TIMESTAMPDIFF()</literal> function resulted in
+          invalid view. (Bug #12298)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          Comparison of InnoDB multi-part primary keys that include
+          <literal>VARCHAR</literal> columns can result in incorrect
+          results. (Bug #12340)
+        </para>
+      </listitem>
 
       <listitem>
         <para>