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

[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.3045 05/07/16 19:50:14 paul@stripped +3 -0
  Document bugfix. (Bug #6987)
  Document bugfix. (Bug #7291)
  Document bugfix. (Bug #9881)
  Document bugfix. (Bug #11482)
  Document bugfix. (Bug #11819)
  Document bugfix. (Bug #11868)

  refman-5.0/news.xml
    1.62 05/07/16 19:50:13 paul@stripped +20 -0
    Sync.

  refman-4.1/news.xml
    1.53 05/07/16 19:50:13 paul@stripped +25 -0
    Sync.

  refman/news.xml
    1.75 05/07/16 19:49:19 paul@stripped +45 -0
    Document bugfix. (Bug #6987)
    Document bugfix. (Bug #7291)
    Document bugfix. (Bug #9881)
    Document bugfix. (Bug #11482)
    Document bugfix. (Bug #11819)
    Document bugfix. (Bug #11868)

# 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:	frost.snake.net
# Root:	/Volumes/frost2/MySQL/bk/mysqldoc

--- 1.52/refman-4.1/news.xml	2005-07-16 19:04:22 -05:00
+++ 1.53/refman-4.1/news.xml	2005-07-16 19:50:13 -05:00
@@ -195,6 +195,25 @@
    <itemizedlist>
 
     <listitem><para>
+     Corrected a problem with the optimizer incorrectly adding
+     <literal>NOT NULL</literal> constraints, producing in incorrect
+     results for complex queries. (Bug #11482)
+    </para></listitem>
+
+    <listitem><para>
+     Corrected an optimizer problem with <literal>NOT NULL</literal>
+     constraints within a subquery in an <literal>UPDATE</literal>
+     statement that resulted in a server crash. (Bug #11868)
+    </para></listitem>
+
+    <listitem><para>
+     Creating a table with a <literal>SET</literal> or
+     <literal>ENUM</literal> column with the <literal>DEFAULT
+     0</literal> clause caused a server crash if the table's character
+     set was <literal>utf8</literal>. (Bug #11819)
+    </para></listitem>
+
+    <listitem><para>
      In SQL prepared statements, comparisons could fail for values not
      equally space-padded. For example, <literal>SELECT 'a' =
      'a&nbsp;';</literal> returns 1, but <literal>PREPARE s FROM 'SELECT
@@ -306,6 +325,12 @@
 
 <!-- NOTE: No need to start every item with "Fixed..."; sufficient to
      describe the  issue that was fixed. Use past tense. -->
+
+    <listitem><para>
+     Added a missing mutex when rotating the relay logs. Also, the
+     server now logs an error message if the size of a relay log cannot
+     be read. (Bug #6987)
+    </para></listitem>
 
     <listitem><para>
      <command>mysqldump</command> could crash for illegal or nonexistent

--- 1.61/refman-5.0/news.xml	2005-07-16 19:04:22 -05:00
+++ 1.62/refman-5.0/news.xml	2005-07-16 19:50:13 -05:00
@@ -252,6 +252,26 @@
    <itemizedlist>
 
     <listitem><para>
+     For a stored procedure defined with <literal>SQL SECURITY
+     DEFINER</literal> characteristic,
<literal>CURRENT_USER()</literal>
+     incorrectly reported the use invoking the procedure, not the user
+     who defined it. (Bug #7291)
+    </para></listitem>
+
+    <listitem><para>
+     Creating a table with a <literal>SET</literal> or
+     <literal>ENUM</literal> column with the <literal>DEFAULT
+     0</literal> clause caused a server crash if the table's character
+     set was <literal>utf8</literal>. (Bug #11819)
+    </para></listitem>
+
+    <listitem><para>
+     With strict SQL mode enabled, <literal>ALTER TABLE</literal>
+     reported spurious <quote>Invalid default value</quote> messages for
+     columns that had no <literal>DEFAULT</literal> clause. (Bug #9881)
+    </para></listitem>
+
+    <listitem><para>
      In SQL prepared statements, comparisons could fail for values not
      equally space-padded. For example, <literal>SELECT 'a' =
      'a&nbsp;';</literal> returns 1, but <literal>PREPARE s FROM 'SELECT

--- 1.74/refman/news.xml	2005-07-16 19:04:23 -05:00
+++ 1.75/refman/news.xml	2005-07-16 19:49:19 -05:00
@@ -244,6 +244,26 @@
    <itemizedlist>
 
     <listitem><para>
+     For a stored procedure defined with <literal>SQL SECURITY
+     DEFINER</literal> characteristic,
<literal>CURRENT_USER()</literal>
+     incorrectly reported the use invoking the procedure, not the user
+     who defined it. (Bug #7291)
+    </para></listitem>
+
+    <listitem><para>
+     Creating a table with a <literal>SET</literal> or
+     <literal>ENUM</literal> column with the <literal>DEFAULT
+     0</literal> clause caused a server crash if the table's character
+     set was <literal>utf8</literal>. (Bug #11819)
+    </para></listitem>
+
+    <listitem><para>
+     With strict SQL mode enabled, <literal>ALTER TABLE</literal>
+     reported spurious <quote>Invalid default value</quote> messages for
+     columns that had no <literal>DEFAULT</literal> clause. (Bug #9881)
+    </para></listitem>
+
+    <listitem><para>
      In SQL prepared statements, comparisons could fail for values not
      equally space-padded. For example, <literal>SELECT 'a' =
      'a&nbsp;';</literal> returns 1, but <literal>PREPARE s FROM 'SELECT
@@ -5014,6 +5034,25 @@
    <itemizedlist>
 
     <listitem><para>
+     Corrected a problem with the optimizer incorrectly adding
+     <literal>NOT NULL</literal> constraints, producing in incorrect
+     results for complex queries. (Bug #11482)
+    </para></listitem>
+
+    <listitem><para>
+     Corrected an optimizer problem with <literal>NOT NULL</literal>
+     constraints within a subquery in an <literal>UPDATE</literal>
+     statement that resulted in a server crash. (Bug #11868)
+    </para></listitem>
+
+    <listitem><para>
+     Creating a table with a <literal>SET</literal> or
+     <literal>ENUM</literal> column with the <literal>DEFAULT
+     0</literal> clause caused a server crash if the table's character
+     set was <literal>utf8</literal>. (Bug #11819)
+    </para></listitem>
+
+    <listitem><para>
      In SQL prepared statements, comparisons could fail for values not
      equally space-padded. For example, <literal>SELECT 'a' =
      'a&nbsp;';</literal> returns 1, but <literal>PREPARE s FROM 'SELECT
@@ -5134,6 +5173,12 @@
      describe the issue that was fixed. Use past tense. -->
 
    <itemizedlist>
+
+    <listitem><para>
+     Added a missing mutex when rotating the relay logs. Also, the
+     server now logs an error message if the size of a relay log cannot
+     be read. (Bug #6987)
+    </para></listitem>
 
     <listitem><para>
      <command>mysqldump</command> could crash for illegal or nonexistent