Fixed MysqlPooledConnection.close()
            calling wrong event type.
          
            Fixed StringIndexOutOfBoundsException in
            PreparedStatement.setClob().
          
4.1 Column Metadata fixes.
            Remove synchronization from
            Driver.connect() and
            Driver.acceptsUrl().
          
            IOExceptions during a transaction now
            cause the Connection to be closed.
          
            Fixed missing conversion for YEAR type in
            ResultSetMetaData.getColumnTypeName().
          
            Don't pick up indexes that start with pri
            as primary keys for
            DBMD.getPrimaryKeys().
          
            Throw SQLExceptions when trying to do
            operations on a forcefully closed
            Connection (that is, when a communication
            link failure occurs).
          
            You can now toggle profiling on/off using
            Connection.setProfileSql(boolean).
          
Fixed charset issues with database metadata (charset was not getting set correctly).
            Updatable ResultSets can now be created
            for aliased tables/columns when connected to MySQL-4.1 or
            newer.
          
            Fixed LOAD DATA LOCAL INFILE bug when
            file > max_allowed_packet.
          
            Fixed escaping of 0x5c ('\') character
            for GBK and Big5 charsets.
          
            Fixed ResultSet.getTimestamp() when
            underlying field is of type DATE.
          
            Ensure that packet size from
            alignPacketSize() does not exceed
            max_allowed_packet (JVM bug)
          
            Don't reset Connection.isReadOnly() when
            autoReconnecting.
          
É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.

