(mysql.info) news-5-0-x
Info Catalog
(mysql.info) news
(mysql.info) news
(mysql.info) mysql-cluster-change-history
D.1 Changes in release 5.0.x (Production)
=========================================
Menu
* news-5-0-20 Changes in release 5.0.20 (Not yet released)
* news-5-0-19 Changes in release 5.0.19 (Not yet released)
* news-5-0-18 Changes in release 5.0.18 (21 December 2005)
* news-5-0-17 Changes in release 5.0.17 (14 December 2005)
* news-5-0-16 Changes in release 5.0.16 (10 November 2005)
* news-5-0-15 Changes in release 5.0.15 (19 October 2005: Production)
* news-5-0-14 Changes in release 5.0.14 (Not released)
* news-5-0-13 Changes in release 5.0.13 (22 Sept 2005: Release Candidate)
* news-5-0-12 Changes in release 5.0.12 (02 Sept 2005)
* news-5-0-11 Changes in release 5.0.11 (06 Aug 2005)
* news-5-0-10 Changes in release 5.0.10 (27 July 2005)
* news-5-0-9 Changes in release 5.0.9 (15 July 2005)
* news-5-0-8 Changes in release 5.0.8 (Not released)
* news-5-0-7 Changes in release 5.0.7 (10 June 2005)
* news-5-0-6 Changes in release 5.0.6 (26 May 2005)
* news-5-0-5 Changes in release 5.0.5 (Not released)
* news-5-0-4 Changes in release 5.0.4 (16 Apr 2005)
* news-5-0-3 Changes in release 5.0.3 (23 Mar 2005: Beta)
* news-5-0-2 Changes in release 5.0.2 (01 Dec 2004)
* news-5-0-1 Changes in release 5.0.1 (27 Jul 2004)
* news-5-0-0 Changes in release 5.0.0 (22 Dec 2003: Alpha)
The following changelog shows what has been done in the 5.0 tree:
* Basic support for read-only server side cursors. For information
about using cursors within stored routines, see cursors.
For information about using cursors from within the C API, see
mysql-stmt-attr-set.
* Basic support for (updatable) views. See, for example,
create-view.
* Basic support for stored procedures and functions (SQL:2003
style). See stored-procedures.
* Initial support for rudimentary triggers.
* Added `SELECT INTO LIST_OF_VARS', which can be of mixed (that is,
global and local) types. See select-into-statement.
* Removed the update log. It is fully replaced by the binary log.
If the MySQL server is started with -log-update, it is translated
to -log-bin (or ignored if the server is explicitly started with
-log-bin), and a warning message is written to the error log.
Setting `SQL_LOG_UPDATE' silently sets `SQL_LOG_BIN' instead (or
do nothing if the server is explicitly started with -log-bin).
* Support for the `ISAM' storage engine has been removed. If you
have `ISAM' tables, you should convert them before upgrading. See
upgrading-from-4-1.
* Support for `RAID' options in `MyISAM' tables has been removed. If
you have tables that use these options, you should convert them
before upgrading. See upgrading-from-4-1.
* User variable names are now case insensitive: If you do `SET
@a=10;' then `SELECT @A;' now returns `10'. Case sensitivity of a
variable's value depends on the collation of the value.
* Strict mode, which in essence means that you get an error instead
of a warning when inserting an incorrect value into a column. See
server-sql-mode.
* `VARCHAR' and `VARBINARY' columns remember end space. A
`VARCHAR()' or `VARBINARY' column can contain up to 65,535
characters or bytes, respectively.
* `MEMORY' (`HEAP') tables can have `VARCHAR()' columns.
* When using a constant string or a function that generates a string
result in `CREATE ... SELECT', MySQL creates the result field
based on the maximum length of the string or expression:
*Maximum Length* *Data type*
= 0 `CHAR(0)'
< 512 `VARCHAR(MAX_LENGTH)'
>= 512 `TEXT'
For a full list of changes, please refer to the changelog sections for
each individual 5.0.x release.
Info Catalog
(mysql.info) news
(mysql.info) news
(mysql.info) mysql-cluster-change-history
automatically generated byinfo2html