Below is the list of changes that have just been committed into a local
mysqldoc repository of jon. When jon 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.2845 05/06/22 03:17:33 jon@stripped +3 -0
Documenting bugfixes:
Bug#7422
Bug#6883
Bug#11060
Bug#7015
Bug#10840
refman/news.xml
1.11 05/06/22 03:17:32 jon@stripped +104 -19
Documenting bugfixes:
Bug#7422
Bug#6883
Bug#11060
Bug#7015
Bug#10840
refman-5.0/news.xml
1.7 05/06/22 03:17:31 jon@stripped +104 -19
Documenting bugfixes:
Bug#7422
Bug#6883
Bug#11060
Bug#7015
Bug#10840
refman-4.1/news.xml
1.7 05/06/22 03:17:31 jon@stripped +104 -19
Documenting bugfixes:
Bug#7422
Bug#6883
Bug#11060
Bug#7015
Bug#10840
# 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: jon
# Host: gigan.site
# Root: /home/jon/bk/mysqldoc
--- 1.6/refman-4.1/news.xml 2005-06-21 21:18:34 +10:00
+++ 1.7/refman-4.1/news.xml 2005-06-22 03:17:31 +10:00
@@ -225,12 +225,22 @@
Functionality added or changed:
</para>
-<itemizedlist>
-<listitem><para>
- New <literal>SQL_MODE</literal> - <literal>NO_ENGINE_SUBSTITUTION</literal>
-Prevents automatic substitution of storage engine when the requested storage engine is disabled or not compiled in. (Bug #6877)
-</para></listitem>
-</itemizedlist>
+ <itemizedlist>
+
+ <listitem>
+ <para>New <literal>SQL_MODE</literal> - <literal>NO_ENGINE_SUBSTITUTION</literal>
+ Prevents automatic substitution of storage engine when the requested
+ storage engine is disabled or not compiled in. (Bug #6877)</para>
+ </listitem>
+
+ <listitem>
+ <para>The statements <literal>CREATE TABLE</literal>,
+ <literal>TRUNCATE TABLE</literal>, <literal>DROP
+ DATABASE</literal>, and <literal>CREATE DATABASE</literal> cause
+ an implicit commit.</para>
+ </listitem>
+
+ </itemizedlist>
<para>
Bugs fixed:
@@ -238,9 +248,50 @@
<itemizedlist>
-<listitem><para>
- Fixed error where a three byte buffer overflow in the client functions (when reading a command from the user) may cause improper exiting of the client. (Bug #10841)
-</para></listitem>
+ <listitem>
+ <para>An <literal>ORDER BY</literal> clause sometimes had no
+ effect on the ordering of a result when selecting specific columns
+ (as opposed to using <literal>SELECT *</literal>) from a view.
+ (Bug#7422)</para>
+ </listitem>
+
+ <listitem>
+ <para>Some data definition statements (<literal>CREATE
+ TABLE</literal> where the table was not a temporary table,
+ <literal>TRUNCATE TABLE</literal>, <literal>DROP
+ DATABASE</literal>, and <literal>CREATE DATABASE</literal>) were
+ not being written to the binary log after a
+ <literal>ROLLBACK</literal>. This also caused problems with
+ replication. (Bug#6883)</para>
+ </listitem>
+
+
+ <listitem>
+ <para>Calling a stored procedure that made use of an
+ <literal>INSERT ... SELECT ... UNION SELECT ...</literal> query
+ caused a server crash. (Bug#11060)</para>
+ </listitem>
+
+ <listitem>
+ <para>Selecting from a view defined using <literal>SELECT
+ SUM(DISTINCT ...)</literal> caused an error; attempting to execute
+ a <literal>SELECT * FROM INFORMATION_SCHEMA.TABLES</literal> query
+ after defining such a view crashed the server. (Bug#7015)</para>
+ </listitem>
+
+ <listitem>
+ <para>The <command>mysql</command> client would output a prompt
+ twice following input of very long strings, because it incorrectly
+ assumed that a call to the <command>_cgets()</command> function
+ would clear the input buffer. (Bug#10840)
+ </para>
+ </listitem>
+
+ <listitem><para>
+ A three byte buffer overflow in the client functions caused improper
+ exiting of the client when reading a command from the user. (Bug
+ #10841)
+ </para></listitem>
<listitem><para>
Fixed a problem where a stored procedure caused a server crash if
@@ -4127,9 +4178,14 @@
file.
</para></listitem>
-<listitem><para>
- The <literal>table</literal>, <literal>type</literal>, and <literal>rows</literal> columns of <literal>EXPLAIN</literal> output can now be <literal>NULL</literal>. This is required for using <literal>EXPLAIN</literal> on <literal>SELECT</literal> queries that use no tables (i.e. <literal>EXPLAIN SELECT 1</literal>). (Bug #9899)
-</para></listitem>
+ <listitem>
+ <para>The <literal>table</literal>, <literal>type</literal>, and
+ <literal>rows</literal> columns of <literal>EXPLAIN</literal>
+ output can now be <literal>NULL</literal>. This is required for
+ using <literal>EXPLAIN</literal> on <literal>SELECT</literal>
+ queries that use no tables, such as
+ <literal>EXPLAIN SELECT 1</literal>). (Bug #9899)</para>
+ </listitem>
</itemizedlist>
@@ -4139,14 +4195,26 @@
<itemizedlist>
+<!-- NOTE: No need to start every item with "Fixed..."; sufficient to
+ describe the issue that was fixed. -->
-<listitem><para>
- Fixed bug in <literal>FIELD()</literal> function where value list contains <literal>NULL</literal>. (Bug #10944)
-</para></listitem>
-
-<listitem><para>
- Fixed error where a three byte buffer overflow in the client functions (when reading a command from the user) may cause improper exiting of the client. (Bug #10841)
-</para></listitem>
+ <listitem>
+ <para>The <command>mysql</command> client would output a prompt
+ twice following input of very long strings, because it incorrectly
+ assumed that a call to the <command>_cgets()</command> function
+ would clear the input buffer. (Bug#10840)</para>
+ </listitem>
+
+ <listitem>
+ <para>A bug in <literal>FIELD()</literal> function caused the value
+ list to contain <literal>NULL</literal>. (Bug #10944)</para>
+ </listitem>
+
+ <listitem>
+ <para>A three byte buffer overflow in the client functions could
+ cause improper exiting of the client when reading a command from
+ the user. (Bug #10841)</para>
+ </listitem>
<listitem><para>
Fixed a problem with the <literal>cp1250_czech_cs</literal>
@@ -6579,6 +6647,13 @@
queries; unless <literal>--short-form</literal> is used.
</para></listitem>
+ <listitem>
+ <para>The statements <literal>CREATE TABLE</literal>,
+ <literal>TRUNCATE TABLE</literal>, <literal>DROP
+ DATABASE</literal>, and <literal>CREATE DATABASE</literal> cause
+ an implicit commit.</para>
+ </listitem>
+
</itemizedlist>
<para>
@@ -6586,6 +6661,16 @@
</para>
<itemizedlist>
+
+ <listitem>
+ <para>Some data definition statements (<literal>CREATE
+ TABLE</literal> where the table was not a temporary table,
+ <literal>TRUNCATE TABLE</literal>, <literal>DROP
+ DATABASE</literal>, and <literal>CREATE DATABASE</literal>) were
+ not being written to the binary log after a
+ <literal>ROLLBACK</literal>. This also caused problems with
+ replication. (Bug#6883)</para>
+ </listitem>
<listitem><para>
Fixed incorrect referencing to column by name from subquery to
--- 1.6/refman-5.0/news.xml 2005-06-21 21:18:36 +10:00
+++ 1.7/refman-5.0/news.xml 2005-06-22 03:17:31 +10:00
@@ -225,12 +225,22 @@
Functionality added or changed:
</para>
-<itemizedlist>
-<listitem><para>
- New <literal>SQL_MODE</literal> - <literal>NO_ENGINE_SUBSTITUTION</literal>
-Prevents automatic substitution of storage engine when the requested storage engine is disabled or not compiled in. (Bug #6877)
-</para></listitem>
-</itemizedlist>
+ <itemizedlist>
+
+ <listitem>
+ <para>New <literal>SQL_MODE</literal> - <literal>NO_ENGINE_SUBSTITUTION</literal>
+ Prevents automatic substitution of storage engine when the requested
+ storage engine is disabled or not compiled in. (Bug #6877)</para>
+ </listitem>
+
+ <listitem>
+ <para>The statements <literal>CREATE TABLE</literal>,
+ <literal>TRUNCATE TABLE</literal>, <literal>DROP
+ DATABASE</literal>, and <literal>CREATE DATABASE</literal> cause
+ an implicit commit.</para>
+ </listitem>
+
+ </itemizedlist>
<para>
Bugs fixed:
@@ -238,9 +248,50 @@
<itemizedlist>
-<listitem><para>
- Fixed error where a three byte buffer overflow in the client functions (when reading a command from the user) may cause improper exiting of the client. (Bug #10841)
-</para></listitem>
+ <listitem>
+ <para>An <literal>ORDER BY</literal> clause sometimes had no
+ effect on the ordering of a result when selecting specific columns
+ (as opposed to using <literal>SELECT *</literal>) from a view.
+ (Bug#7422)</para>
+ </listitem>
+
+ <listitem>
+ <para>Some data definition statements (<literal>CREATE
+ TABLE</literal> where the table was not a temporary table,
+ <literal>TRUNCATE TABLE</literal>, <literal>DROP
+ DATABASE</literal>, and <literal>CREATE DATABASE</literal>) were
+ not being written to the binary log after a
+ <literal>ROLLBACK</literal>. This also caused problems with
+ replication. (Bug#6883)</para>
+ </listitem>
+
+
+ <listitem>
+ <para>Calling a stored procedure that made use of an
+ <literal>INSERT ... SELECT ... UNION SELECT ...</literal> query
+ caused a server crash. (Bug#11060)</para>
+ </listitem>
+
+ <listitem>
+ <para>Selecting from a view defined using <literal>SELECT
+ SUM(DISTINCT ...)</literal> caused an error; attempting to execute
+ a <literal>SELECT * FROM INFORMATION_SCHEMA.TABLES</literal> query
+ after defining such a view crashed the server. (Bug#7015)</para>
+ </listitem>
+
+ <listitem>
+ <para>The <command>mysql</command> client would output a prompt
+ twice following input of very long strings, because it incorrectly
+ assumed that a call to the <command>_cgets()</command> function
+ would clear the input buffer. (Bug#10840)
+ </para>
+ </listitem>
+
+ <listitem><para>
+ A three byte buffer overflow in the client functions caused improper
+ exiting of the client when reading a command from the user. (Bug
+ #10841)
+ </para></listitem>
<listitem><para>
Fixed a problem where a stored procedure caused a server crash if
@@ -4127,9 +4178,14 @@
file.
</para></listitem>
-<listitem><para>
- The <literal>table</literal>, <literal>type</literal>, and <literal>rows</literal> columns of <literal>EXPLAIN</literal> output can now be <literal>NULL</literal>. This is required for using <literal>EXPLAIN</literal> on <literal>SELECT</literal> queries that use no tables (i.e. <literal>EXPLAIN SELECT 1</literal>). (Bug #9899)
-</para></listitem>
+ <listitem>
+ <para>The <literal>table</literal>, <literal>type</literal>, and
+ <literal>rows</literal> columns of <literal>EXPLAIN</literal>
+ output can now be <literal>NULL</literal>. This is required for
+ using <literal>EXPLAIN</literal> on <literal>SELECT</literal>
+ queries that use no tables, such as
+ <literal>EXPLAIN SELECT 1</literal>). (Bug #9899)</para>
+ </listitem>
</itemizedlist>
@@ -4139,14 +4195,26 @@
<itemizedlist>
+<!-- NOTE: No need to start every item with "Fixed..."; sufficient to
+ describe the issue that was fixed. -->
-<listitem><para>
- Fixed bug in <literal>FIELD()</literal> function where value list contains <literal>NULL</literal>. (Bug #10944)
-</para></listitem>
-
-<listitem><para>
- Fixed error where a three byte buffer overflow in the client functions (when reading a command from the user) may cause improper exiting of the client. (Bug #10841)
-</para></listitem>
+ <listitem>
+ <para>The <command>mysql</command> client would output a prompt
+ twice following input of very long strings, because it incorrectly
+ assumed that a call to the <command>_cgets()</command> function
+ would clear the input buffer. (Bug#10840)</para>
+ </listitem>
+
+ <listitem>
+ <para>A bug in <literal>FIELD()</literal> function caused the value
+ list to contain <literal>NULL</literal>. (Bug #10944)</para>
+ </listitem>
+
+ <listitem>
+ <para>A three byte buffer overflow in the client functions could
+ cause improper exiting of the client when reading a command from
+ the user. (Bug #10841)</para>
+ </listitem>
<listitem><para>
Fixed a problem with the <literal>cp1250_czech_cs</literal>
@@ -6579,6 +6647,13 @@
queries; unless <literal>--short-form</literal> is used.
</para></listitem>
+ <listitem>
+ <para>The statements <literal>CREATE TABLE</literal>,
+ <literal>TRUNCATE TABLE</literal>, <literal>DROP
+ DATABASE</literal>, and <literal>CREATE DATABASE</literal> cause
+ an implicit commit.</para>
+ </listitem>
+
</itemizedlist>
<para>
@@ -6586,6 +6661,16 @@
</para>
<itemizedlist>
+
+ <listitem>
+ <para>Some data definition statements (<literal>CREATE
+ TABLE</literal> where the table was not a temporary table,
+ <literal>TRUNCATE TABLE</literal>, <literal>DROP
+ DATABASE</literal>, and <literal>CREATE DATABASE</literal>) were
+ not being written to the binary log after a
+ <literal>ROLLBACK</literal>. This also caused problems with
+ replication. (Bug#6883)</para>
+ </listitem>
<listitem><para>
Fixed incorrect referencing to column by name from subquery to
--- 1.10/refman/news.xml 2005-06-21 21:18:02 +10:00
+++ 1.11/refman/news.xml 2005-06-22 03:17:32 +10:00
@@ -225,12 +225,22 @@
Functionality added or changed:
</para>
-<itemizedlist>
-<listitem><para>
- New <literal>SQL_MODE</literal> - <literal>NO_ENGINE_SUBSTITUTION</literal>
-Prevents automatic substitution of storage engine when the requested storage engine is disabled or not compiled in. (Bug #6877)
-</para></listitem>
-</itemizedlist>
+ <itemizedlist>
+
+ <listitem>
+ <para>New <literal>SQL_MODE</literal> - <literal>NO_ENGINE_SUBSTITUTION</literal>
+ Prevents automatic substitution of storage engine when the requested
+ storage engine is disabled or not compiled in. (Bug #6877)</para>
+ </listitem>
+
+ <listitem>
+ <para>The statements <literal>CREATE TABLE</literal>,
+ <literal>TRUNCATE TABLE</literal>, <literal>DROP
+ DATABASE</literal>, and <literal>CREATE DATABASE</literal> cause
+ an implicit commit.</para>
+ </listitem>
+
+ </itemizedlist>
<para>
Bugs fixed:
@@ -238,9 +248,50 @@
<itemizedlist>
-<listitem><para>
- Fixed error where a three byte buffer overflow in the client functions (when reading a command from the user) may cause improper exiting of the client. (Bug #10841)
-</para></listitem>
+ <listitem>
+ <para>An <literal>ORDER BY</literal> clause sometimes had no
+ effect on the ordering of a result when selecting specific columns
+ (as opposed to using <literal>SELECT *</literal>) from a view.
+ (Bug#7422)</para>
+ </listitem>
+
+ <listitem>
+ <para>Some data definition statements (<literal>CREATE
+ TABLE</literal> where the table was not a temporary table,
+ <literal>TRUNCATE TABLE</literal>, <literal>DROP
+ DATABASE</literal>, and <literal>CREATE DATABASE</literal>) were
+ not being written to the binary log after a
+ <literal>ROLLBACK</literal>. This also caused problems with
+ replication. (Bug#6883)</para>
+ </listitem>
+
+
+ <listitem>
+ <para>Calling a stored procedure that made use of an
+ <literal>INSERT ... SELECT ... UNION SELECT ...</literal> query
+ caused a server crash. (Bug#11060)</para>
+ </listitem>
+
+ <listitem>
+ <para>Selecting from a view defined using <literal>SELECT
+ SUM(DISTINCT ...)</literal> caused an error; attempting to execute
+ a <literal>SELECT * FROM INFORMATION_SCHEMA.TABLES</literal> query
+ after defining such a view crashed the server. (Bug#7015)</para>
+ </listitem>
+
+ <listitem>
+ <para>The <command>mysql</command> client would output a prompt
+ twice following input of very long strings, because it incorrectly
+ assumed that a call to the <command>_cgets()</command> function
+ would clear the input buffer. (Bug#10840)
+ </para>
+ </listitem>
+
+ <listitem><para>
+ A three byte buffer overflow in the client functions caused improper
+ exiting of the client when reading a command from the user. (Bug
+ #10841)
+ </para></listitem>
<listitem><para>
Fixed a problem where a stored procedure caused a server crash if
@@ -4127,9 +4178,14 @@
file.
</para></listitem>
-<listitem><para>
- The <literal>table</literal>, <literal>type</literal>, and <literal>rows</literal> columns of <literal>EXPLAIN</literal> output can now be <literal>NULL</literal>. This is required for using <literal>EXPLAIN</literal> on <literal>SELECT</literal> queries that use no tables (i.e. <literal>EXPLAIN SELECT 1</literal>). (Bug #9899)
-</para></listitem>
+ <listitem>
+ <para>The <literal>table</literal>, <literal>type</literal>, and
+ <literal>rows</literal> columns of <literal>EXPLAIN</literal>
+ output can now be <literal>NULL</literal>. This is required for
+ using <literal>EXPLAIN</literal> on <literal>SELECT</literal>
+ queries that use no tables, such as
+ <literal>EXPLAIN SELECT 1</literal>). (Bug #9899)</para>
+ </listitem>
</itemizedlist>
@@ -4139,14 +4195,26 @@
<itemizedlist>
+<!-- NOTE: No need to start every item with "Fixed..."; sufficient to
+ describe the issue that was fixed. -->
-<listitem><para>
- Fixed bug in <literal>FIELD()</literal> function where value list contains <literal>NULL</literal>. (Bug #10944)
-</para></listitem>
-
-<listitem><para>
- Fixed error where a three byte buffer overflow in the client functions (when reading a command from the user) may cause improper exiting of the client. (Bug #10841)
-</para></listitem>
+ <listitem>
+ <para>The <command>mysql</command> client would output a prompt
+ twice following input of very long strings, because it incorrectly
+ assumed that a call to the <command>_cgets()</command> function
+ would clear the input buffer. (Bug#10840)</para>
+ </listitem>
+
+ <listitem>
+ <para>A bug in <literal>FIELD()</literal> function caused the value
+ list to contain <literal>NULL</literal>. (Bug #10944)</para>
+ </listitem>
+
+ <listitem>
+ <para>A three byte buffer overflow in the client functions could
+ cause improper exiting of the client when reading a command from
+ the user. (Bug #10841)</para>
+ </listitem>
<listitem><para>
Fixed a problem with the <literal>cp1250_czech_cs</literal>
@@ -6579,6 +6647,13 @@
queries; unless <literal>--short-form</literal> is used.
</para></listitem>
+ <listitem>
+ <para>The statements <literal>CREATE TABLE</literal>,
+ <literal>TRUNCATE TABLE</literal>, <literal>DROP
+ DATABASE</literal>, and <literal>CREATE DATABASE</literal> cause
+ an implicit commit.</para>
+ </listitem>
+
</itemizedlist>
<para>
@@ -6586,6 +6661,16 @@
</para>
<itemizedlist>
+
+ <listitem>
+ <para>Some data definition statements (<literal>CREATE
+ TABLE</literal> where the table was not a temporary table,
+ <literal>TRUNCATE TABLE</literal>, <literal>DROP
+ DATABASE</literal>, and <literal>CREATE DATABASE</literal>) were
+ not being written to the binary log after a
+ <literal>ROLLBACK</literal>. This also caused problems with
+ replication. (Bug#6883)</para>
+ </listitem>
<listitem><para>
Fixed incorrect referencing to column by name from subquery to
| Thread |
|---|
| • bk commit - mysqldoc@docsrva tree (jon:1.2845) | jon | 21 Jun |
