Oracle 5.0 Reference Manual page 169

converting all tables that use
be removed. Verify that they are empty, and then remove them manually. (If they are not empty, this
indicates that there is some
• As of MySQL 5.0.25, the
the language used to display day and month names and abbreviations. This variable affects the
output from the
See Section 10.7, "MySQL Server Locale
• In MySQL 5.0.6, binary logging of stored routines and triggers was changed. This change has
implications for security, replication, and data recovery, as discussed in
Logging of Stored
• As of MySQL 5.0.28,
it invokes
specify another server explicitly. If you previously relied on the implicit invocation of mysqld-max,
you should use an appropriate option now.
SQL Changes
• Known issue: Prior to MySQL 5.0.46, the parser accepted invalid code in SQL condition handlers,
leading to server crashes or unexpected execution behavior in stored programs. Specifically, the
parser permitted a condition handler to refer to labels for blocks that enclose the handler declaration.
This was incorrect because block label scope does not include the code for handlers declared within
the labeled block.
As of 5.0.46, the parser rejects this invalid construct, but if you upgrade in place (without dumping
and reloading your databases), existing handlers that contain the construct still are invalid even if
they appear to function as you expect and should be rewritten.
To find affected handlers, use mysqldump to dump all stored procedures and functions, triggers,
and events. Then attempt to reload them into an upgraded server. Handlers that contain illegal label
references will be rejected.
For more information about condition handlers and writing them to avoid invalid jumps, see
Section 13.6.7.2,
• Known issue: The fix for Bug #23491 introduced a problem with
used by mysqldump. This causes an incompatibility when upgrading from versions affected by that
bug fix (MySQL 5.0.40 through 5.0.43, MySQL 5.1.18 through 5.1.19): If you use
upgrading from an affected version and reload the data after upgrading to a higher version, you must
drop and recreate your views.
• Incompatible change: The parser accepted statements that contained
properly closed with */, such as
unclosed /*-comments now are rejected with a syntax error.
This fix has the potential to cause incompatibilities. Because of Bug #26302, which caused the
trailing
*/
possible that objects of those types may have been stored with definitions that now will be rejected
as syntactically invalid. Such objects should be dropped and re-created so that their definitions do
not contain truncated comments. If a stored object definition contains only a single statement (does
not use a
should be moved to follow the statement or the object should be rewritten to use a
block. For example, this statement:
CREATE PROCEDURE p() SELECT 1 /* my comment */ ;
Can be rewritten in either of these ways:
CREATE PROCEDURE p() SELECT 1; /* my comment */
CREATE PROCEDURE p() BEGIN SELECT 1 /* my comment */ ; END;
RAID
RAID
lc_time_names
DATE_FORMAT()
Programs".
mysqld_safe
unless a
mysqld --mysqld
"DECLARE ... HANDLER
to be truncated from comments in views, stored routines, triggers, and events, it is
block) and contains a comment within the statement, the comment
BEGIN ... END
Upgrading MySQL
options, these RAID-related subdirectories still will exist but can
table that has not been converted.)
[462] system variable specifies the locale that controls
[921], [923]
DAYNAME()
Support".
no longer implicitly invokes
[247] or
--mysqld-version
Syntax".
2. As of MySQL 5.0.50, statements that contain
SELECT 1 /* +
149
and [926]
MONTHNAME()
Section 18.6, "Binary
if it exists. Instead,
mysqld-max
[247] option is given to
VIEW, which is
SHOW CREATE
mysqldump
/* ... */
functions.
before
that were not
BEGIN ... END