Oracle 5.0 Reference Manual page 172

• Incompatible change: Before MySQL 5.0.8, conversion of
adding zero produced a result in
YYYYMMDDHHMMSS.000000
• Incompatible change: In MySQL 5.0.6, the behavior of
INTO OUTFILE
values both are empty. Formerly, a column was read or written using the display width of the column.
For example,
and written using a field width wide enough to hold all values in the field. However, data files written
before this change was made might not be reloaded correctly with
5.0.6 and up. This change also affects data files read by
--tab, which use
see Section 13.2.6,
• Incompatible change: Before MySQL 5.0.2,
default as of 5.0.2 is to return session values, which is incompatible with previous versions. To issue
a
SHOW STATUS
like this:
SHOW /*!50002 GLOBAL */ STATUS;
• Incompatible change: User variables are not case sensitive in MySQL 5.0. In MySQL 4.1,
= 0; SET @X = 1; SELECT @x;
one variable and returns 1. Replication setups that rely on the old behavior may be affected by this
change.
• Some keywords may be reserved in MySQL 5.0 that were not reserved in MySQL 4.1. See
Section 9.3, "Reserved
• The
LOAD DATA FROM MASTER
Section 13.4.2.2,
• As of MySQL 5.0.25,
COLUMNS
• Comparisons made between
not do so in 5.0. Values of these types are imprecise in all MySQL versions, and you are strongly
advised to avoid such comparisons as
version you are using. See
• As of MySQL 5.0.3,
Section 11.1.1, "Numeric Type
• MySQL 5.0.2 adds several SQL modes that enable stricter control over rejecting records that
have invalid or missing values. See
"Constraints on Invalid
capability for storing incorrect dates such as '2004-02-31', you should start the server with
sql_mode="TRADITIONAL,ALLOW_INVALID_DATES"
• As of MySQL 5.0.2, the
and DATABASES, respectively. (While "schemata" is grammatically correct and even appears in some
MySQL 5.0 system database and table names, it cannot be used as a keyword.)
C API Changes
• Incompatible change: Because the MySQL 5.0 server has a new implementation of the
data type, a problem may occur if the server is used by older clients that still are linked against
MySQL 4.1 client libraries. If a client uses the binary client/server protocol to execute prepared
statements that generate result sets containing numeric values, an error will be raised:
unsupported buffer type: 246'
format.
has changed when the
was read or written using a field with a width of 4. Now columns are read
INT(4)
LOAD DATA INFILE
"LOAD DATA INFILE
statement that will retrieve global status values for all versions of MySQL, write it
Words".
"LOAD DATA FROM MASTER
TIMESTAMP
and INFORMATION_SCHEMA, rather than as NULL.
FLOAT
Section C.5.5.8, "Problems with Floating-Point
is a separate data type, not a synonym for TINYINT(1). See
BIT
Overview".
Data". If you want to enable this control but continue to use MySQL's
SCHEMA
Upgrading MySQL
format. The result of
YYYYMMDDHHMMSS
FIELDS TERMINATED BY
and
SELECT ... INTO
Syntax".
SHOW STATUS
created two variables and returned 0. In MySQL 5.0, it creates
and
LOAD TABLE FROM MASTER
Syntax", for recommended alternatives.
columns that are
NOT NULL
or values that happened to work in MySQL 4.1 may
DOUBLE
col_name=some_double, regardless of the MySQL
WHERE
Section 5.1.7, "Server SQL
and keywords are accepted as synonyms for
SCHEMAS
152
values to numeric form by
DATETIME
DATETIME+0
and
LOAD DATA INFILE
and
FIELDS ENCLOSED BY
LOAD DATA INFILE
and written by
mysqlimport
OUTFILE. For more information,
returned global status values. The
statements are deprecated. See
now are reported that way by
Values".
Modes", and Section 1.8.6.3,
[495].
is now in
SELECT ...
for MySQL
mysqldump
SET @x
SHOW
--
DATABASE
DECIMAL
'Using