Changed charsToByte in
SingleByteCharConverter to be non-static.
Changed SingleByteCharConverter to use
lazy initialization of each converter.
Fixed charset handling in Fields.java.
Implemented Connection.nativeSQL().
More robust escape tokenizer: Recognize
-- comments, and allow nested escape
sequences (see
testsuite.EscapeProcessingTest).
DBMD.getImported/ExportedKeys() now
handles multiple foreign keys per table.
Fixed ResultSetMetaData.getPrecision()
returning incorrect values for some floating-point types.
Fixed
ResultSetMetaData.getColumnTypeName()
returning BLOB for
TEXT and TEXT for
BLOB types.
Fixed Buffer.isLastDataPacket() for 4.1
and newer servers.
Added CLIENT_LONG_FLAG to be able to get
more column flags (isAutoIncrement()
being the most important).
Because of above, implemented
ResultSetMetaData.isAutoIncrement() to
use Field.isAutoIncrement().
Honor lower_case_table_names when enabled
in the server when doing table name comparisons in
DatabaseMetaData methods.
Some MySQL-4.1 protocol support (extended field info from selects).
Use non-aliased table/column names and database names to
fullly qualify tables and columns in
UpdatableResultSet (requires MySQL-4.1 or
newer).
Allow user to alter behavior of
Statement/
PreparedStatement.executeBatch() via
continueBatchOnError property (defaults
to true).
Check for connection closed in more
Connection methods
(createStatement,
prepareStatement,
setTransactionIsolation,
setAutoCommit).
More robust implementation of updatable result sets. Checks that all primary keys of the table have been selected.
LOAD DATA LOCAL INFILE ... now works, if
your server is configured to allow it. Can be turned off
with the allowLoadLocalInfile property
(see the README).
Substitute '?' for unknown character
conversions in single-byte character sets instead of
'\0'.
NamedPipeSocketFactory now works (only
intended for Windows), see README for
instructions.
É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.
