( Upgrading-from-4

Info Catalog ( Upgrade ( Upgrade ( Upgrading-from-4
 2.10.1 Upgrading from Version 4.1 to 5.0
 In general, you should do the following when upgrading to MySQL 5.0
 from 4.1:
    * Check the items in the change list found later in this section to
      see whether any of them might affect your applications.
    * Read the 5.0 news items to see what significant new features you
      can use in 5.0.   News-5.0.x.
    * If you are running MySQL Server on Windows, see  Windows
      upgrading.  Also, two of the Windows MySQL servers were renamed.
       Windows select server.
    * MySQL 5.0 adds support for stored procedures. This support
      requires the `proc' table in the `mysql' database.  To create this
      file, you should run the `mysql_fix_privilege_tables' script as
      described in  Upgrading-grant-tables.
    * MySQL 5.0 adds support for views. This support requires the extra
      privilege columns in the `user' and `db' tables in the `mysql'
      database.  To create these columns, you should run the
      `mysql_fix_privilege_tables' script as described in 
    * If you are using replication, see  Replication Upgrade for
      information on upgrading your replication setup.
    * MySQL 5.0.2 adds several new SQL modes that allow stricter control
      over rejecting records that have invalid or missing values.  
      Server SQL mode.   constraint invalid data.  If you want
      to enable this control but continue to use MySQL's 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 `SCHEMA' and `SCHEMAS' keywords are
      accepted as synonyms for `DATABASE' and `DATABASES'.
    * The update log is removed in MySQL 5.0.
 The following list describes changes that may affect applications and
 that you should watch out for when upgrading to version 5.0:
    * The update log is removed, so if you enabled it in the past, you
      should enable the binary log instead.   News-5.0.x.
    * User variables are not case sensitive. In MySQL 4.1, `SET @x = 0;
      SET @X = 1; SELECT @x;' creates two variables and returns `0'. In
      MySQL 5.0, it creates one variable and returns `1'.
    * API change: the `reconnect' flag in the `MYSQL' structure is set
      to 0 by `mysql_real_connect()'. Only those client programs which
      didn't explicitly set this flag to 0 or 1 after
      `mysql_real_connect()' will experience a change. Having automatic
      reconnection enabled by default was considered too dangerous
      (after reconnection, table locks, temporary tables, user and
      session variables are lost).
Info Catalog ( Upgrade ( Upgrade ( Upgrading-from-4
automatically generated byinfo2html