Fonctionnalité ajoutée ou modifiée :
            The KILL statement now takes
            CONNECTION and QUERY
            modifiers. The first is the same as KILL
            with no modifier (it kills a given connection thread). The
            second kills only the statement currently being executed by
            the connection.
          
            Added TIMESTAMPADD() and
            TIMESTAMPDIFF() functions.
          
            Added WEEK and QUARTER
            values as INTERVAL arguments for the
            DATE_ADD() and
            DATE_SUB() functions.
          
            New binary log format that enables replication of these
            session variables: sql_mode,
            SQL_AUTO_IS_NULL,
            FOREIGN_KEY_CHECKS (which was already
            replicated since 4.0.14, but here it's done more efficiently
            and takes less space in the binary logs),
            UNIQUE_CHECKS. Other variables (like
            character sets, SQL_SELECT_LIMIT, ...)
            will be replicated in upcoming 5.0.x releases.
          
            Implemented Index Merge optimization for
            OR clauses. See
            Section 7.2.6, « Optimisation de combinaison d'index ».
          
Basic support for stored procedures (SQL:2003 style). See Chapitre 19, Procédures stockées et fonctions.
            Added SELECT INTO
            , which can
            be of mixed (that is, global and local) types. See
            Section 19.2.9.3, « Syntaxe de list_of_varsSELECT ... INTO ».
          
Easier replication upgrade (5.0.0 masters can read older binary logs and 5.0.0 slaves can read older relay logs). See Section 6.5, « Compatibilité de la réplication entre les versions de MySQL » for more details). The format of the binary log and relay log is changed compared to that of MySQL 4.1 and older.
            Important note: If you
            upgrade to MySQL 4.1.1 or higher, it is difficult to
            downgrade back to 4.0 or 4.1.0! That is because, for earlier
            versions, InnoDB is not aware of multiple
            tablespaces.
          
Bogues corrigés :
This is a translation of the MySQL Reference Manual that can be found at dev.mysql.com. The original Reference Manual is in English, and this translation is not necessarily as up to date as the English version.
