Ant build was corrupting included
            jar files, fixed (bug 487669).
          
            Fixed extra memory allocation in
            MysqlIO.readPacket() (bug 488663).
          
            Implementation of
            DatabaseMetaData.getExported/ImportedKeys()
            and getCrossReference().
          
Full synchronization on methods modifying instance and class-shared references, driver should be entirely thread-safe now (please let me know if you have problems).
            DataSource implementations moved to
            org.gjt.mm.mysql.jdbc2.optional package,
            and (initial) implementations of
            PooledConnectionDataSource and
            XADataSource are in place (thanks to Todd
            Wolff for the implementation and testing of
            PooledConnectionDataSource with IBM
            WebSphere 4).
          
Added detection of network connection being closed when reading packets (thanks to Todd Lizambri).
Fixed quoting error with escape processor (bug 486265).
            Report batch update support through
            DatabaseMetaData (bug 495101).
          
            Fixed off-by-one-hour error in
            PreparedStatement.setTimestamp() (bug
            491577).
          
            Removed concatenation support from driver (the
            || operator), as older versions of
            VisualAge seem to be the only thing that use it, and it
            conflicts with the logical || operator.
            You will need to start mysqld with the
            --ansi flag to use the
            || operator as concatenation (bug
            491680).
          
            Fixed casting bug in PreparedStatement
            (bug 488663).
          
Ésta es una traducción del manual de referencia de MySQL, que puede encontrarse en dev.mysql.com. El manual de referencia original de MySQL está escrito en inglés, y esta traducción no necesariamente está tan actualizada como la versión original. Para cualquier sugerencia sobre la traducción y para señalar errores de cualquier tipo, no dude en dirigirse a mysql-es@vespito.com.

