[+/-]
End of Product Lifecycle. Active development and support for MySQL Database Server version 5.0 has ended. However, there is still extended support available. For details, see http://www.mysql.com/about/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/about/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 5.0. Please consider upgrading to a recent version.
An overview of which features were added in MySQL 5.0 can be found here: Section 1.5, “What Is New in MySQL 5.0”. The list following summarizes what has been done in the 5.0 tree.
For a full list of changes, please refer to the changelog sections for each individual 5.0 release.
For discussion of upgrade issues that you many encounter for upgrades to MySQL 5.0 from MySQL 4.1, see Section 2.18.1.2, “Upgrading from MySQL 4.1 to 5.0”.
VARCHAR
and
VARBINARY
columns retain trailing
spaces. A VARCHAR()
or
VARBINARY
column can contain up
to 65,535 characters or bytes, respectively.
Strict SQL mode, which causes an error instead of a warning when inserting an incorrect value into a column. See Section 5.1.7, “Server SQL Modes”.
A new fixed-point math library supports precision math,
resulting in more accurate results when working with the
DECIMAL
and
NUMERIC
data types. For details,
see Section 11.13, “Precision Math”.
Basic support for views. See Section 18.4, “Using Views”.
Basic support for stored procedures and functions (SQL:2003 style). See Section 18.2, “Using Stored Routines (Procedures and Functions)”.
Basic support for triggers. See Section 18.3, “Using Triggers”.
Basic support for read-only server side cursors. For information
about using cursors within stored routines, see
Section 12.7.5, “Cursors”. For information about using cursors
from within the C API, see
Section 20.8.7.3, “mysql_stmt_attr_set()
”.
Support for SELECT INTO
, where the
variables can be a mix of global and local types. See
Section 12.7.3.3, “list_of_vars
SELECT ... INTO
Statement”.
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 column based on the maximum length of the
string or expression:
Maximum Length | Data type |
= 0 | CHAR(0) |
< 512 | VARCHAR( |
>= 512 | TEXT |
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
).
Removed support for the ISAM
storage engine.
If you have ISAM
tables, you should convert
them before upgrading. See
Section 2.18.1.2, “Upgrading from MySQL 4.1 to 5.0”.
Removed support for RAID
options in
MyISAM
tables. If you have tables that use
these options, you should convert them before upgrading. See
Section 2.18.1.2, “Upgrading from MySQL 4.1 to 5.0”.
User Comments
Add your own comment.