Add unsigned attribute to
            DatabaseMetaData.getColumns() output in
            the TYPE_NAME column.
          
            Added failOverReadOnly property, to allow
            end-user to configure state of connection
            (read-only/writable) when failed over.
          
            Backported “change user” and “reset
            server state” functionality from 3.1 branch, to allow
            clients of MysqlConnectionPoolDataSource
            to reset server state on getConnection()
            on a pooled connection.
          
Don't escape SJIS/GBK/BIG5 when using MySQL-4.1 or newer.
            Allow url parameter for
            MysqlDataSource and
            MysqlConnectionPool
            DataSource so that passing of other
            properties is possible from inside appservers.
          
            Map duplicate key and foreign key errors to SQLState of
            23000.
          
Backport documentation tooling from 3.1 branch.
            Return creating statement for ResultSets
            created by getGeneratedKeys(). (Bug#2957)
          
            Allow java.util.Date to be sent in as
            parameter to
            PreparedStatement.setObject(), converting
            it to a Timestamp to maintain full
            precision. (Bug#103).
          
            Don't truncate BLOB or
            CLOB values when using
            setBytes() and/or
            setBinary/CharacterStream(). (Bug#2670).
          
            Dynamically configure character set mappings for field-level
            character sets on MySQL-4.1.0 and newer using SHOW
            COLLATION when connecting.
          
            Map binary character set to
            US-ASCII to support
            DATETIME charset recognition for servers
            >= 4.1.2.
          
            Use SET character_set_results during
            initialization to allow any charset to be returned to the
            driver for result sets.
          
            Use charsetnr returned during connect to
            encode queries before issuing SET NAMES
            on MySQL >= 4.1.0.
          
            Add helper methods to ResultSetMetaData
            (getColumnCharacterEncoding() and
            getColumnCharacterSet()) to allow
            end-users to see what charset the driver thinks it should be
            using for the column.
          
            Only set character_set_results for MySQL
            >= 4.1.0.
          
            StringUtils.escapeSJISByteStream() not
            covering all eastern double-byte charsets correctly. (Bug#3511)
          
            Renamed
            StringUtils.escapeSJISByteStream() to
            more appropriate
            escapeEasternUnicodeByteStream().
          
            Not specifying database in URL caused
            MalformedURL exception. (Bug#3554)
          
            Auto-convert MySQL encoding names to Java encoding names if
            used for characterEncoding property.
          
Added encoding names that are recognized on some JVMs to fix case where they were reverse-mapped to MySQL encoding names incorrectly.
            Use junit.textui.TestRunner for all unit
            tests (to allow them to be run from the command line outside
            of Ant or Eclipse).
          
            UpdatableResultSet not picking up default
            values for moveToInsertRow(). (Bug#3557)
          
Inconsistent reporting of data type. The server still doesn't return all types for *BLOBs *TEXT correctly, so the driver won't return those correctly. (Bug#3570)
            DBMD.getSQLStateType() returns incorrect
            value. (Bug#3520)
          
            Fixed regression in
            PreparedStatement.setString() and eastern
            character encodings.
          
            Made StringRegressionTest 4.1-unicode
            aware.
          
É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.

