(mysql.info) news-5-0-5
Info Catalog
(mysql.info) news-5-0-6
(mysql.info) news-5-0-x
(mysql.info) news-5-0-4
D.1.16 Changes in release 5.0.5 (Not released)
----------------------------------------------
No public release of MySQL 5.0.5 was made. The changes described in
this section are available in MySQL 5.0.6.
Functionality added or changed:
* Added support for the `BIT' data type to the `MEMORY', `InnoDB',
and `BDB' storage engines.
* `SHOW VARIABLES' no longer displays the deprecated `log_update'
system variable. (Bug #9738 (http://bugs.mysql.com/9738))
* The behavior controlled by the -innodb-fast-shutdown option now
can be changed at runtime by setting the value of the global
`innodb_fast_shutdown' system variable. 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 down, `InnoDB' will just flush its
logs and shut down brutally (and quickly) as if a MySQL crash had
occurred; no committed transaction will be lost, but a crash
recovery will be done at next startup.
Bugs fixed:
* *Security fix:* If `mysqld' was started with
-user=NON_EXISTENT_USER, it would run using the privileges of the
account it was invoked from, even if that was `root'. (Bug #9833
(http://bugs.mysql.com/9833))
* Corrected a failure to resolve a column reference correctly for a
`LEFT JOIN' that compared a join column to an `IN' subquery. (Bug
#9338 (http://bugs.mysql.com/9338))
* 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 (`Can't find record in '''). (Bug #9703
(http://bugs.mysql.com/9703))
* 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 (http://bugs.mysql.com/9103))
* Fixed a string-length comparison problem that caused `mysql' to
fail loading dump files containing certain ‘`\'’-sequences.
(Bug #9756 (http://bugs.mysql.com/9756))
* 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
(http://bugs.mysql.com/6106), Bug #6107
(http://bugs.mysql.com/6107))
* Use of a subquery that used `WITH ROLLUP' in the `FROM' clause of
the main query sometimes resulted in a `Column cannot be null'
error. (Bug #9681 (http://bugs.mysql.com/9681))
* Fixed a memory leak that occurred when selecting from a view that
contained a subquery. (Bug #10107 (http://bugs.mysql.com/10107))
* Fixed an optimizer bug in computing the union of two ranges for
the `OR' operator. (Bug #9348 (http://bugs.mysql.com/9348))
* Fixed a segmentation fault in `mysqlcheck' that occurred when the
last table checked in -auto-repair mode returned an error (such as
the table being a `MERGE' table). (Bug #9492
(http://bugs.mysql.com/9492))
* `SET @var= CAST(NULL AS [INTEGER|CHAR])' now sets the result type
of the variable to `INTEGER'/`CHAR'. (Bug #6598
(http://bugs.mysql.com/6598))
* Incorrect results were returned for queries of the form `SELECT
... LEFT JOIN ... WHERE EXISTS (SUBQUERY)', where the subquery
selected rows based on an `IS NULL' condition. (Bug #9516
(http://bugs.mysql.com/9516))
* Executing `LOCK TABLES' and then calling a stored procedure caused
an error and resulting in the server thinking that no stored
procedures exist. (Bug #9566 (http://bugs.mysql.com/9566))
* Selecting from a view containing a subquery caused the server to
hang. (Bug #8490 (http://bugs.mysql.com/8490))
* Within a stored procedure, attempting to execute a multiple-table
`UPDATE' failed with a `Table 'TBL_NAME' was locked with a READ
lock and can't be updated' error. (Bug #9486
(http://bugs.mysql.com/9486))
* Starting `mysqld' with the -skip-innodb and
-default-storage-engine=innodb (or -default-table-type=innodb
caused a server crash. (Bug #9815 (http://bugs.mysql.com/9815))
* Queries containing `CURRENT_USER()' incorrectly were registered in
the query cache. (Bug #9796 (http://bugs.mysql.com/9796))
* Setting the `storage_engine' system variable to `MEMORY'
succeeded, but retrieving the variable resulted in a value of
`HEAP' (the old name for the `MEMORY' storage engine) rather than
`MEMORY'. (Bug #10039 (http://bugs.mysql.com/10039))
* `mysqlshow' displayed an incorrect row count for tables. (Bug
#9391 (http://bugs.mysql.com/9391))
* The server died with signal 11 if a non-existent location was
specified for the location of the binary log. Now the server exits
after printing an appropriate error message. (Bug #9542
(http://bugs.mysql.com/9542))
* Fixed a problem in the client/server protocol where the server
closed the connection before sending the final error message. The
problem could show up as a `Lost connection to MySQL server during
query' when attempting to connect to access a non-existent
database. (Bug #6387 (http://bugs.mysql.com/6387), Bug #9455
(http://bugs.mysql.com/9455))
* Fixed a `readline'-related crash in `mysql' when the user pressed
Control-R. (Bug #9568 (http://bugs.mysql.com/9568))
* For stored functions that should return a `YEAR' value, corrected
a failure of the value to be in `YEAR' format. (Bug #8861
(http://bugs.mysql.com/8861))
* Fixed a server crash resulting from invocation of a stored
function that returned a value having an `ENUM' or `SET' data type.
(Bug #9775 (http://bugs.mysql.com/9775))
* Fixed a server crash resulting from invocation of a stored
function that returned a value having a `BLOB' data type. (Bug
#9102 (http://bugs.mysql.com/9102))
* Fixed a server crash resulting from invocation of a stored
function that returned a value having a `BIT' data type. (Bug
#7648 (http://bugs.mysql.com/7648))
* `TIMEDIFF()' with a negative time first argument and positive time
second argument produced incorrect results. (Bug #8068
(http://bugs.mysql.com/8068))
* Fixed a problem with `OPTIMIZE TABLE' for `InnoDB' tables being
written twice to the binary log. (Bug #9149
(http://bugs.mysql.com/9149))
* `InnoDB': Prevent `ALTER TABLE' from changing the storage engine
if there are foreign key constraints on the table. (Bug #5574
(http://bugs.mysql.com/5574), Bug #5670
(http://bugs.mysql.com/5670))
* `InnoDB': Fixed a bug where next-key locking doesn't allow the
insert which does not produce a phantom. (Bug #9354
(http://bugs.mysql.com/9354)) If the range is of type `'a' <=
uniquecolumn', `InnoDB' lock only the RECORD, if the record with
the column value `'a'' exists in a CLUSTERED index. This allows
inserts before a range.
* `InnoDB': When `FOREIGN_KEY_CHECKS=0', `ALTER TABLE' and `RENAME
TABLE' will ignore any type incompatibilities between referencing
and referenced columns. Thus, it will be possible to convert the
character sets of columns that participate in a foreign key. Be
sure to convert all tables before modifying any data! (Bug #9802
(http://bugs.mysql.com/9802))
* Provide more informative error messages in clustered setting when
a query is issued against a table that has been modified by
another `mysqld' server. (Bug #6762 (http://bugs.mysql.com/6762))
Info Catalog
(mysql.info) news-5-0-6
(mysql.info) news-5-0-x
(mysql.info) news-5-0-4
automatically generated byinfo2html