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.2920 05/04/28 11:00:23 paul@stripped +1 -0
manual.texi:
Document bugfix. (Bug #9103)
Document bugfix. (Bug #9017)
Document bugfix. (Bug #9681)
Document bugfix. (Bug #10107)
Document bugfix. (Bug #10162)
Document bugfix. (Bug #9911)
Document bugfix. (Bug #8877)
Docs/manual.texi
1.2783 05/04/28 10:59:32 paul@stripped +11 -1
Document bugfix. (Bug #9103)
Docs/manual.texi
1.2782 05/04/28 10:47:41 paul@stripped +10 -2
Document bugfix. (Bug #9017)
Docs/manual.texi
1.2781 05/04/28 10:40:26 paul@stripped +15 -7
Document bugfix. (Bug #9681)
Docs/manual.texi
1.2780 05/04/28 10:29:15 paul@stripped +3 -0
Document bugfix. (Bug #10107)
Docs/manual.texi
1.2779 05/04/28 10:25:27 paul@stripped +9 -4
Document bugfix. (Bug #10162)
Docs/manual.texi
1.2778 05/04/28 10:18:37 paul@stripped +6 -0
Document bugfix. (Bug #9911)
Docs/manual.texi
1.2777 05/04/28 10:09:22 paul@stripped +9 -1
Document bugfix. (Bug #8877)
# 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.2776/Docs/manual.texi 2005-04-27 21:34:43 -05:00
+++ 1.2783/Docs/manual.texi 2005-04-28 10:59:32 -05:00
@@ -33806,8 +33806,10 @@
cannot select a single row based on the key value). If the key that is
used matches only a few rows, this is a good join type.
+@c Note: The "or <=>" applies only to ref, not to eq_ref.
+
@code{ref} can be used for indexed columns that are compared using the @code{=}
-operator.
+or @code{<=>} operator.
In the following examples, MySQL can use a @code{ref} join to process
@var{ref_table}:
@@ -87429,7 +87431,7 @@
argument is the value for the option. If the option is an integer, then
@code{arg} should point to the value of the integer.
-Possible options values:
+Possible @code{option} values:
@multitable @columnfractions .42 .20 .38
@item @strong{Option} @tab @strong{Argument Type} @tab @strong{Function}
@@ -99277,6 +99279,13 @@
Bugs fixed:
@itemize @bullet
@item
+The optimizer was choosing suboptimal execution plans for certain outer
+joins where the right table of a left join (or left table of a right join)
+had both @code{ON} and @code{WHERE} conditions. (Bug #10162)
+@item
+@code{RENAME TABLE} for an @code{ARCHIVE} table failed if the @file{.arn} file
+was not present. (Bug #9911)
+@item
Invoking a stored function that executed a @code{SHOW} statement resulted in a
server crash. (Bug #8408)
@item
@@ -99300,16 +99309,9 @@
Added support for the @code{BIT} data type to the @code{MEMORY},
@code{InnoDB}, and @code{BDB} storage engines.
@item
-Fixed a string-length comparison problem that caused @command{mysql} to fail
-loading dump files containing certain @samp{\}-sequences. (Bug #9756)
-@item
@code{SHOW VARIABLES} no longer displays the deprecated @code{log_update}
system variable. (Bug #9738)
@item
-Fixed a failure to resolve a column reference properly when an outer join
-involving a view contained a subquery and the column was used in the subquery
-and the outer query. (Bug #6106, Bug #6107)
-@item
@code{--innodb-fast-shutdown} is now also settable on the fly (global variable
@code{innodb_fast_shutdown}). It now accepts values 0, 1 and 2 (except on
Netware where 2 is disabled); if set to 2, then when the MySQL server shuts
@@ -99326,6 +99328,24 @@
@code{--user=@var{non_existent_user}}, it would run using the privileges of the
account it was invoked from, even if that was @code{root}. (Bug #9833)
@item
+Multiple-table updates could produce spurious data-truncation warnings if
+they used a join across columns that are indexed using a column prefix.
+(Bug #9103)
+@item
+Fixed a string-length comparison problem that caused @command{mysql} to fail
+loading dump files containing certain @samp{\}-sequences. (Bug #9756)
+@item
+Fixed a failure to resolve a column reference properly when an outer join
+involving a view contained a subquery and the column was used in the subquery
+and the outer query. (Bug #6106, Bug #6107)
+@item
+Use of a subquery that used @code{WITH ROLLUP} in the @code{FROM} clause
+of the main query sometimes resulted in a @code{Column cannot be null}
+error. (Bug #9681)
+@item
+Fixed a memory leak that occurred when selecting from a view that contained
+a subquery. (Bug #10107)
+@item
Fixed an optimizer bug in computing the union of two ranges for the @code{OR}
operator. (Bug #9348)
@item
@@ -99453,6 +99473,14 @@
Bugs fixed:
@itemize @bullet
@item
+The use of @code{XOR} together with @code{NOT ISNULL()} erroneously resulted
+in some outer joins being converted to inner joins by the optimizer.
+(Bug #9017)
+@item
+Fixed an optimizer problem where extraneous comparisons between @code{NULL}
+values in indexed columns were being done for operators such as @code{=} that
+are never true for @code{NULL}. (Bug #8877)
+@item
Fixed the client/server protocol for prepared statements so that reconnection
works properly when the connection is killed while reconnect is enabled.
(Bug #8866)
@@ -100928,10 +100956,11 @@
the character sets of columns that participate in a foreign key. Be sure
to convert all tables before modifying any data! (Bug #9802)
@item
-Previously, an @code{Illegal mix of collations} error occurred when mixing
-strings from same character set when one had a non-binary collation and
-the other a binary collation. Now the binary collation takes precedence,
-so that both strings are treated as having the binary collation.
+Previously in MySQL 4.1, an @code{Illegal mix of collations} error occurred
+when mixing strings from same character set when one had a non-binary
+collation and the other a binary collation. Now the binary collation takes
+precedence, so that both strings are treated as having the binary collation.
+This restores compatibility with MySQL 4.0 behavior.
@end itemize
@@ -100943,6 +100972,21 @@
@code{--user=@var{non_existent_user}}, it would run using the privileges of the
account it was invoked from, even if that was @code{root}. (Bug #9833)
@item
+Multiple-table updates could produce spurious data-truncation warnings if
+they used a join across columns that are indexed using a column prefix.
+(Bug #9103)
+@item
+Use of a subquery that used @code{WITH ROLLUP} in the @code{FROM} clause
+of the main query sometimes resulted in a @code{Column cannot be null}
+error. (Bug #9681)
+@item
+@code{RENAME TABLE} for an @code{ARCHIVE} table failed if the @file{.arn} file
+was not present. (Bug #9911)
+@item
+Fixed an optimizer problem where extraneous comparisons between @code{NULL}
+values in indexed columns were being done for operators such as @code{=} that
+are never true for @code{NULL}. (Bug #8877)
+@item
@code{SELECT ROUND(@var{expr})} produced a different result than
@code{CREATE TABLE ... SELECT ROUND(@var{expr})}. (Bug #9837)
@item
@@ -101097,6 +101141,10 @@
Bugs fixed:
@itemize @bullet
+@item
+The use of @code{XOR} together with @code{NOT ISNULL()} erroneously resulted
+in some outer joins being converted to inner joins by the optimizer.
+(Bug #9017)
@item
Fixed @code{utf8_spanish2_ci} and @code{ucs2_spanish2_ci} collations to not
consider @samp{r} equal to @samp{rr}. If you upgrade to this version from
| Thread |
|---|
| • bk commit - mysqldoc tree (paul:1.2920) | paul | 28 Apr |
