bk commit - mysqldoc tree (paul:1.2644)

[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.2644 05/03/06 19:02:34 paul@stripped +1 -0
  manual.texi:
    Document bugfix. (Bug #8306)
    Document bugfix. (Bug #8235)
    Document bugfix. (Bug #8136)
    Document bugfix. (Bug #8054)
    Document bugfix. (Bug #8050)
    Document bugfix. (Bug #7945)
    Document bugfix. (Bug #7672)

  Docs/manual.texi
    1.2469 05/03/06 19:02:17 paul@stripped +12 -0
    Document bugfix. (Bug #8306)

  Docs/manual.texi
    1.2468 05/03/06 18:36:21 paul@stripped +8 -0
    Document bugfix. (Bug #8235)

  Docs/manual.texi
    1.2467 05/03/06 18:21:20 paul@stripped +8 -0
    Document bugfix. (Bug #8136)

  Docs/manual.texi
    1.2466 05/03/06 18:11:05 paul@stripped +7 -4
    Document bugfix. (Bug #8054)

  Docs/manual.texi
    1.2465 05/03/06 18:08:56 paul@stripped +4 -1
    Document bugfix. (Bug #8050)

  Docs/manual.texi
    1.2464 05/03/06 18:01:51 paul@stripped +12 -0
    Document bugfix. (Bug #7945)

  Docs/manual.texi
    1.2463 05/03/06 17:46:17 paul@stripped +4 -0
    Document bugfix. (Bug #7672)

# 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.2462/Docs/manual.texi	2005-03-05 21:45:55 -06:00
+++ 1.2469/Docs/manual.texi	2005-03-06 19:02:17 -06:00
@@ -96836,6 +96836,30 @@
 Bugs fixed:
 @itemize @bullet
 @item
+Corruption of @code{MyISAM} table indexes could occur with @code{TRUNCATE
+TABLE} if the table had already been opened. For example, this was possible
+if the table had been opened implicitly by selecting from a @code{MERGE}
+table that mapped to the @code{MyISAM} table. The server now issues an error
+message for @code{TRUNCATE TABLE} under these conditions. (Bug #8306)
+@item
+Setting the connection collation to a value different from the server
+collation followed by a @code{CREATE TABLE} statement that included a quoted
+default value resulted in a server crash. (Bug #8235)
+@item
+Fixed handling of table-name matching in @command{mysqlhotcopy} to
+accommodate @code{DBD::mysql} 2.9003 and up (which implement identifier
+quoting). (Bug #8136)
+@item
+Selecting from a view defined as a join caused a server crash if the query
+cache was enabled. (Bug #8054)
+@item
+Results in the query cache generated from a view were not properly invalidated
+after @code{ALTER VIEW} or @code{DROP VIEW} on that view. (Bug #8050)
+@item
+@code{FOUND_ROWS()} returned an incorrect value after a @code{SELECT
+SQL_CALC_FOUND_ROWS DISTINCT} statement that selected constants and included
+@code{GROUP BY} and @code{LIMIT} clauses. (Bug #7945)
+@item
 Selecting from an @code{INFORMATION_SCHEMA} table combined with a subselect on
 an @code{INFORMATION_SCHEMA} table caused an error with the message
 @code{Table @var{tbl_name} is corrupted}. (Bug #8164)
@@ -97740,6 +97764,16 @@
 Bugs fixed:
 @itemize @bullet
 @item
+Corruption of @code{MyISAM} table indexes could occur with @code{TRUNCATE
+TABLE} if the table had already been opened. For example, this was possible
+if the table had been opened implicitly by selecting from a @code{MERGE}
+table that mapped to the @code{MyISAM} table. The server now issues an error
+message for @code{TRUNCATE TABLE} under these conditions. (Bug #8306)
+@item
+Fixed handling of table-name matching in @command{mysqlhotcopy} to
+accommodate @code{DBD::mysql} 2.9003 and up (which implement identifier
+quoting). (Bug #8136)
+@item
 In the @code{mysql_real_escape_string()} C API function, when a multi-byte
 character is encountered that is illegal in the current character set,
 escape only the first byte, not each byte. This avoids creating a valid
@@ -97887,6 +97921,10 @@
 Functionality added or changed:
 @itemize @bullet
 @item
+Setting the connection collation to a value different from the server
+collation followed by a @code{CREATE TABLE} statement that included a quoted
+default value resulted in a server crash. (Bug #8235)
+@item
 Thread stack size was increased from 192KB to 256KB on Linux/IA-64
 (too small stack size was causing server crashes on some queries).
 (Bug #8391)
@@ -97933,10 +97971,14 @@
 Bugs fixed:
 @itemize @bullet
 @item
+@code{FOUND_ROWS()} returned an incorrect value after a @code{SELECT
+SQL_CALC_FOUND_ROWS DISTINCT} statement that selected constants and included
+@code{GROUP BY} and @code{LIMIT} clauses. (Bug #7945)
+@item
 Fixed a bug in cardinality estimations for @code{HASH} indexes of
 @code{TEMPORARY} tables created using @code{MEMORY} storage engine.
 As a result queries that were using this index (as shown by @code{EXPLAIN})
-could have returned incorrect results.  (Bug #8371)
+could have returned incorrect results. (Bug #8371)
 @item
 Corrected a problem with references to @code{DUAL} where statements such as
 @code{SELECT 1 AS a FROM DUAL} would succeed but statements such as
@@ -100540,6 +100582,14 @@
 
 Bugs fixed:
 @itemize @bullet
+@item
+@code{FOUND_ROWS()} returned an incorrect value after a @code{SELECT
+SQL_CALC_FOUND_ROWS DISTINCT} statement that selected constants and included
+@code{GROUP BY} and @code{LIMIT} clauses. (Bug #7945)
+@item
+Queries of the form @code{(SELECT ...) ORDER BY ...} were being treated as a
+@code{UNION}.  This improperly resulted in only distinct values being
+returned (because @code{UNION} by default eliminates.) (Bug #7672)
 @item
 Index cardinality was not being updated properly for @code{TEMPOARY} tables
 under some circumstances, such as @code{CREATE TABLE ... SELECT} followed by