- Documentation Library
- Table of Contents
- MySQL 5.0 Manual
- Table of Contents
- C.5.3 Changes in MySQL Connector/J 3.1.x
- C.5.3.1 Changes in MySQL Connector/J 3.1.15 (Not yet released)
- C.5.3.2 Changes in MySQL Connector/J 3.1.14 (10-19-2006)
- C.5.3.3 Changes in MySQL Connector/J 3.1.13 (26 May 2006)
- C.5.3.4 Changes in MySQL Connector/J 3.1.12 (30 November 2005)
- C.5.3.5 Changes in MySQL Connector/J 3.1.11-stable (07 October 2005)
- C.5.3.6 Changes in MySQL Connector/J 3.1.10-stable (23 June 2005)
- C.5.3.7 Changes in MySQL Connector/J 3.1.9-stable (22 June 2005)
- C.5.3.8 Changes in MySQL Connector/J 3.1.8-stable (14 April 2005)
- C.5.3.9 Changes in MySQL Connector/J 3.1.7-stable (18 February 2005)
- C.5.3.10 Changes in MySQL Connector/J 3.1.6-stable (23 December 2004)
- C.5.3.11 Changes in MySQL Connector/J 3.1.5-gamma (02 December 2004)
- C.5.3.12 Changes in MySQL Connector/J 3.1.4-beta (04 September 2004)
- C.5.3.13 Changes in MySQL Connector/J 3.1.3-beta (07 July 2004)
- C.5.3.14 Changes in MySQL Connector/J 3.1.2-alpha (09 June 2004)
- C.5.3.15 Changes in MySQL Connector/J 3.1.1-alpha (14 February 2004)
- C.5.3.16 Changes in MySQL Connector/J 3.1.0-alpha (18 February 2003)
Fixed updatable result set throws ClassCastException when there is row data and moveToInsertRow() is called. (Fixes Bug#20479)
Fixed Updatable result set that contains a BIT column fails when server-side prepared statements are used. (Fixes Bug#20485)
Fixed memory leak with profileSQL=true. (Fixes Bug#16987)
Connection fails to localhost when using timeout and IPv6 is configured. (Fixes Bug#19726)
Fixed NullPointerException in MysqlDataSourceFactory due to Reference containing RefAddrs with null content. (Fixes Bug#16791)
Fixed ResultSet.getShort() for UNSIGNED TINYINT returns incorrect values when using server-side prepared statements. (Fixes Bug#20306)
Fixed can't pool server-side prepared statements, exception raised when re-using them. (Fixes Bug#20687)
Fixed Bug#21062 - ResultSet.getSomeInteger() doesn't work for BIT(>1).
Fixed Bug#18880 - ResultSet.getFloatFromString() can't retrieve values near Float.MIN/MAX_VALUE.
Fixed Bug#20888 - escape of quotes in client-side prepared statements parsing not respected. Patch covers more than bug report, including NO_BACKSLASH_ESCAPES being set, and stacked quote characters forms of escaping (i.e. '' or "").
Fixed Bug#19993 - ReplicationDriver does not always round-robin load balance depending on URL used for slaves list.
Fixed calling toString() on ResultSetMetaData for driver-generated (i.e. from DatabaseMetaData method calls, or from getGeneratedKeys()) result sets would raise a NullPointerException.
Fixed Bug#21207 - Driver throws NPE when tracing prepared statements that have been closed (in asSQL()).
Removed logger autodectection altogether, must now specify logger explicitly if you want to use a logger other than one that logs to STDERR.
Fixed Bug#22290 - Driver issues truncation on write exception when it shouldn't (due to sending big decimal incorrectly to server with server-side prepared statement).
Driver now sends numeric 1 or 0 for client-prepared statement setBoolean() calls instead of '1' or '0'.
Fixed bug where driver would not advance to next host if roundRobinLoadBalance=true and the last host in the list is down.
Fixed Bug#18258 - DatabaseMetaData.getTables(), columns() with bad catalog parameter threw exception rather than return empty result set (as required by spec).
Check and store value for continueBatchOnError property in constructor of Statements, rather than when executing batches, so that Connections closed out from underneath statements don't cause NullPointerExceptions when it's required to check this property.
Fixed bug when calling stored functions, where parameters weren't numbered correctly (first parameter is now the return value, subsequent parameters if specified start at index "2").
É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.
