Oracle 5.0 Reference Manual Download

Page: 169 / 3232

Upgrading MySQL

149

converting all tables that use

RAID

options, these

RAID

-related subdirectories still will exist but can

be removed. Verify that they are empty, and then remove them manually. (If they are not empty, this
indicates that there is some

RAID

table that has not been converted.)

• As of MySQL 5.0.25, the

lc_time_names

[462]

system variable specifies the locale that controls

the language used to display day and month names and abbreviations. This variable affects the
output from the

DATE_FORMAT()

[921]

DAYNAME()

[923]

and

MONTHNAME()

[926]

functions.

See

Section 10.7, “MySQL Server Locale Support”

• 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

Section 18.6, “Binary

Logging of Stored Programs”

• As of MySQL 5.0.28,

mysqld_safe

no longer implicitly invokes

mysqld-max

if it exists. Instead,

it invokes

mysqld

unless a

--mysqld

[247]

--mysqld-version

[247]

option is given to

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, “

DECLARE ... HANDLER

Syntax”

• Known issue: The fix for Bug #23491 introduced a problem with

SHOW CREATE VIEW

, which is

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

mysqldump

before

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

/* ... */

that were not

properly closed with

, such as

SELECT 1 /* + 2

. As of MySQL 5.0.50, statements that contain

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

to be truncated from comments in views, stored routines, triggers, and events, it is

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

Oracle 5.0, Reference Manual

Search results

Summary of Contents for 5.0

Reviews:

Related manuals for 5.0

Brands by name

Popular brands