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.2657 05/05/12 16:06:32 paul@stripped +1 -0
manual.texi:
Document bugfix. (Bug #9186)
Document bugfix. (Bug #8528)
Document bugfix. (Bug #8295)
Document bugfix. (Bug #8296)
Document bugfix. (Bug #9703)
Docs/manual.texi
1.2848 05/05/12 16:05:04 paul@stripped +12 -0
Document bugfix. (Bug #9186)
Docs/manual.texi
1.2847 05/05/12 15:41:17 paul@stripped +3 -0
Document bugfix. (Bug #8528)
Docs/manual.texi
1.2846 05/05/12 15:30:10 paul@stripped +25 -8
Document bugfix. (Bug #8295)
Document bugfix. (Bug #8296)
Docs/manual.texi
1.2845 05/05/12 15:16:36 paul@stripped +8 -0
Document bugfix. (Bug #9703)
# 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.2844/Docs/manual.texi 2005-05-12 08:45:48 -05:00
+++ 1.2848/Docs/manual.texi 2005-05-12 16:05:04 -05:00
@@ -15172,8 +15172,12 @@
@item @code{@ @ @ @ '>} @tab Waiting for next line, collecting a string that begins with a single quote (@samp{'}).
@item @code{@ @ @ @ ">} @tab Waiting for next line, collecting a string that begins with a double quote (@samp{"}).
@item @code{@ @ @ @ `>} @tab Waiting for next line, collecting an identifier that begins with a backtick (@samp{`}).
+@item @code{@ @ @ /*>} @tab Waiting for next line, collecting rest of /* comment.
@end multitable
+The @code{`>} prompt was implemented MySQL 4.0.16. The @code{/*>} prompt was
+implemented in MySQL 4.1.12 and 5.0.6.
+
Multiple-line statements commonly occur by accident when you intend to
issue a command on a single line, but forget the terminating semicolon. In
this case, @command{mysql} waits for more input:
@@ -59698,13 +59702,21 @@
saves space and makes table operations faster. @xref{Storage engines}.
@item
-From MySQL 4.1.0 to MySQL 5.0.2, a @code{CHAR} or @code{VARCHAR} column with a
-length specification greater than 255 is converted to the smallest @code{TEXT}
-type that can hold values of the given length.
-For example, @code{VARCHAR(500)} is converted to @code{TEXT}, and
-@code{VARCHAR(200000)} is converted to @code{MEDIUMTEXT}.
-Note that this conversion results in a change in behavior with regard to
-treatment of trailing spaces.
+From MySQL 4.1.0 to MySQL 5.0.2, a @code{CHAR} or @code{VARCHAR} column
+with a length specification greater than 255 is converted to the smallest
+@code{TEXT} type that can hold values of the given length. For example,
+@code{VARCHAR(500)} is converted to @code{TEXT}, and @code{VARCHAR(200000)}
+is converted to @code{MEDIUMTEXT}. Note that this conversion results in
+a change in behavior with regard to treatment of trailing spaces.
+
+Similar conversions occur for @code{BINARY} and @code{VARBINARY}, except
+that they are converted to a @code{BLOB} type.
+
+From MySQL 5.0.3 on, @code{CHAR} and @code{BINARY} columns with a length
+specification greater than 255 are not silently converted. Instead, an
+error occurs. From MySQL 5.0.6 on, silent conversion of @code{VARCHAR}
+and @code{VARBINARY} columns with a length specification greater than 65,535
+does not occur if strict SQL mode is enabled. Instead, an error occurs.
@item
For a specification of @code{DECIMAL(@var{M},@var{D})}, if @var{M} is not
@@ -99934,6 +99946,15 @@
Functionality added or changed:
@itemize @bullet
@item
+New @code{/*>} prompt for @command{mysql}. This prompt indicates that a
+@code{/* ... */} comment was begun on an earlier line and the closing
+@code{*/} sequence has not yet been seen. (Bug #9186)
+@item
+If strict SQL mode is enabled, @code{VARCHAR} and @code{VARBINARY} columns
+with a length greater than 65,535 no longer are silently converted to
+@code{TEXT} or @code{BLOB} columns. Instead, an error occurs.
+(Bug #8295, Bug #8296)
+@item
The @code{INFORMATION_SCHEMA.SCHEMATA} table now has a
@code{DEFAULT_COLLATION_NAME} column. (Bug #8998)
@item
@@ -99955,6 +99976,12 @@
Bugs fixed:
@itemize @bullet
@item
+Selecting from a single-table view defined on multiple-table views caused a
+server crash. (Bug #8528)
+@item
+If the file named by a @code{--defaults-extra-file} option does not exist or
+is otherwise inaccessible, an error now occurs. (Bug #5056)
+@item
@code{net_read_timeout} and @code{net_write_timeout} were not being respected
on Windows. (Bug #9721)
@item
@@ -100039,11 +100066,18 @@
Bugs fixed:
@itemize @bullet
+
@c Leave the security fix item as first in the list so it stands out better
@item
@strong{Security fix:} If @command{mysqld} was started with
@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
+Fixed a problem where, after an internal temporary table in memory became
+too large and had to be converted to an on-disk table, the error indicator
+was not cleared and the query failed with error 1023 (@code{Can't find record
+in ''}). (Bug #9703)
@item
Multiple-table updates could produce spurious data-truncation warnings if
they used a join across columns that are indexed using a column prefix.
@@ -101668,6 +101702,10 @@
Functionality added or changed:
@itemize @bullet
@item
+New @code{/*>} prompt for @command{mysql}. This prompt indicates that a
+@code{/* ... */} comment was begun on an earlier line and the closing
+@code{*/} sequence has not yet been seen. (Bug #9186)
+@item
Added @code{cp1250_croatian_ci} collation. (Bug #6505)
@item
Updated version of @code{libedit} to 2.9. (Bug #2596)
@@ -101704,11 +101742,13 @@
Bugs fixed:
@itemize @bullet
+
@c Leave the security fix item as first in the list so it stands out better
@item
@strong{Security fix:} If @command{mysqld} was started with
@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
@code{net_read_timeout} and @code{net_write_timeout} were not being respected
on Windows. (Bug #9721)
| Thread |
|---|
| • bk commit - mysqldoc@docsrva tree (paul:1.2657) | paul | 12 May |
