List:Internals« Previous MessageNext Message »
From:paul Date:September 30 2005 7:14pm
Subject:bk commit - mysqldoc@docsrva tree (paul:1.3655)
View as plain text  
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.3655 05/09/30 14:14:48 paul@stripped +3 -0
  news-5.0.xml, news-4.1.xml:
    Document bugfix. (Bug #11139)
  news-5.0.xml:
    Document bugfix. (Bug #6127)
    Document bugfix. (Bug #13455)
    Document bugfix. (Bug #12589)
  news-5.0.xml, news-4.1.xml, news-4.0.xml:
    Document bugfix. (Bug #9112)
  news-5.0.xml:
    Document bugfix. (Bug #12694)
    Document bugfix. (Bug #11680, #13550)
    Document bugfix. (Bug #13545)
    Document bugfix. (Bug #13424)
    Document bugfix. (Bug #13411)
  news-5.0.xml, news-4.1.xml:
    Document bugfix. (Bug #13356)
  news-5.0.xml:
    Add missing 5.0.3 changelog entry

  refman-common/news-5.0.xml
    1.246 05/09/30 14:14:37 paul@stripped +17 -0
    Document bugfix. (Bug #11139)

  refman-common/news-4.1.xml
    1.114 05/09/30 14:14:37 paul@stripped +17 -0
    Document bugfix. (Bug #11139)

  refman-common/news-5.0.xml
    1.245 05/09/30 14:05:03 paul@stripped +7 -0
    Document bugfix. (Bug #6127)

  refman-common/news-5.0.xml
    1.244 05/09/30 13:57:54 paul@stripped +14 -0
    Document bugfix. (Bug #13455)

  refman-common/news-5.0.xml
    1.243 05/09/30 13:51:47 paul@stripped +8 -0
    Document bugfix. (Bug #12589)

  refman-common/news-5.0.xml
    1.242 05/09/30 13:45:12 paul@stripped +7 -0
    Document bugfix. (Bug #9112)

  refman-common/news-4.1.xml
    1.113 05/09/30 13:45:12 paul@stripped +7 -0
    Document bugfix. (Bug #9112)

  refman-common/news-4.0.xml
    1.35 05/09/30 13:45:12 paul@stripped +7 -0
    Document bugfix. (Bug #9112)

  refman-common/news-5.0.xml
    1.241 05/09/30 13:09:49 paul@stripped +0 -2
    Document bugfix. (Bug #12694)

  refman-common/news-5.0.xml
    1.240 05/09/30 13:04:59 paul@stripped +21 -0
    Document bugfix. (Bug #11680, #13550)

  refman-common/news-5.0.xml
    1.239 05/09/30 12:36:25 paul@stripped +8 -0
    Document bugfix. (Bug #13545)

  refman-common/news-5.0.xml
    1.238 05/09/30 12:17:15 paul@stripped +8 -0
    Document bugfix. (Bug #13424)

  refman-common/news-5.0.xml
    1.237 05/09/30 12:12:06 paul@stripped +8 -0
    Document bugfix. (Bug #13411)

  refman-common/news-5.0.xml
    1.236 05/09/30 12:10:14 paul@stripped +7 -0
    Document bugfix. (Bug #13356)

  refman-common/news-4.1.xml
    1.112 05/09/30 12:10:14 paul@stripped +7 -0
    Document bugfix. (Bug #13356)

  refman-common/news-5.0.xml
    1.235 05/09/30 12:01:52 paul@stripped +13 -0
    Add missing 5.0.3 changelog entry

# 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.34/refman-common/news-4.0.xml	2005-09-29 13:15:27 -05:00
+++ 1.35/refman-common/news-4.0.xml	2005-09-30 13:45:12 -05:00
@@ -162,6 +162,13 @@
 
       <listitem>
         <para>
+          Queries against a <literal>MERGE</literal> table that has a
+          composite index could produce incorrect results. (Bug #9112)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
           The counters for the <literal>Key_read_requests</literal>,
           <literal>Key_reads</literal>,
           <literal>Key_write_requests</literal>, and

--- 1.111/refman-common/news-4.1.xml	2005-09-29 13:10:57 -05:00
+++ 1.114/refman-common/news-4.1.xml	2005-09-30 14:14:37 -05:00
@@ -219,6 +219,37 @@
 
       <listitem>
         <para>
+          The <option>--replicate-rewrite-db</option> and
+          <option>--replicate-do-table</option> options did not work for
+          statements in which tables were aliased to names other than
+          those listed by the options. (Bug #11139)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          After running <command>configure</command> with the
+          <option>--with-embedded-privilege-control</option> option, the
+          embedded server failed to build. (Bug #13501)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          Queries against a <literal>MERGE</literal> table that has a
+          composite index could produce incorrect results. (Bug #9112)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          Comparisons involving row constructors containing constants
+          could cause a server crash. (Bug #13356)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
           MySQL would pass an incorrect key length to storage engines
           for <literal>MIN()</literal>. This could cause warnings
           <literal>InnoDB: Warning: using a partial-field key prefix in

--- 1.234/refman-common/news-5.0.xml	2005-09-29 13:16:10 -05:00
+++ 1.246/refman-common/news-5.0.xml	2005-09-30 14:14:37 -05:00
@@ -270,6 +270,109 @@
 
       <listitem>
         <para>
+          The <option>--replicate-rewrite-db</option> and
+          <option>--replicate-do-table</option> options did not work for
+          statements in which tables were aliased to names other than
+          those listed by the options. (Bug #11139)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          After running <command>configure</command> with the
+          <option>--with-embedded-privilege-control</option> option, the
+          embedded server failed to build. (Bug #13501)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          Nested handlers within stored procedures didn't work. (Bug
+          #6127)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          The optimizer chose a less efficient execution plan for
+          <literal><replaceable>col_name</replaceable> BETWEEN
+          <replaceable>const</replaceable> AND
+          <replaceable>const</replaceable></literal> than for
+          <literal><replaceable>col_name</replaceable> =
+          <replaceable>const</replaceable></literal>, even though the
+          two expressions are logically equivalent. Now the optimizer
+          can use the <literal>ref</literal> access method for both
+          expressions. (Bug #13455)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          Incorrect creation of <literal>DECIMAL</literal> local
+          variables in a stored procedure could cause a server crash.
+          (Bug #12589)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          Queries against a <literal>MERGE</literal> table that has a
+          composite index could produce incorrect results. (Bug #9112)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          The server was not rejecting
+          <literal>FLOAT(<replaceable>M</replaceable>,<replaceable>D</replaceable>)</literal>
+          or
+          <literal>DOUBLE(<replaceable>M</replaceable>,<replaceable>D</replaceable>)</literal>
+          columns specifications when <replaceable>M</replaceable> was
+          less than <replaceable>D</replaceable>. (Bug #12694)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          After running <command>configure</command> with the
+          <option>--without-server</option> option, the distribution
+          failed to build. (Bug #11680, Bug #13550)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          Joins nested under <literal>NATURAL</literal> or
+          <literal>USING</literal> joins were sometimes not initialized
+          properly, causing a server crash. (Bug #13545)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          Locking a view with the query cache enabled and
+          <literal>query_cache_wlock_invalidate</literal> enabled could
+          cause a server crash. (Bug #13424)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          A <literal>HAVING</literal> clause that references an
+          unqualified view column name could crash the server. (Bug
+          #13411)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          Comparisons involving row constructors containing constants
+          could cause a server crash. (Bug #13356)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
           <literal>NDB Cluster</literal>: <literal>LOAD DATA
           INFILE</literal> with a large data file failed. (Bug #10694)
         </para>
@@ -6312,6 +6415,19 @@
           <xref linkend="xa"/>. The implementation make the
           <literal>innodb_safe_binlog</literal> system variable
           obsolete, so it has been removed.
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          <command>mysqlbinlog</command> now prints a
+          <literal>ROLLBACK</literal> statement at the end of its
+          output, in case the server crashed while it was in the process
+          of writing the final entry into the last binary log named on
+          the command line. This causes any half-written transaction to
+          be rolled back when the output is executed. The
+          <literal>ROLLBACK</literal> is harmless if the binary log file
+          was written and closed normally.
         </para>
       </listitem>
 
Thread
bk commit - mysqldoc@docsrva tree (paul:1.3655)paul30 Sep