MySQL Forums
Forum List  »  Announcements

MySQL Connector/J 8.0.20 has been released
Posted by: Surabhi Bhat
Date: April 27, 2020 10:52AM




Dear MySQL users,

MySQL Connector/J 8.0.20 is the latest General Availability release of
the MySQL Connector/J 8.0 series.  It is suitable for use with MySQL
Server versions 8.0, 5.7, and 5.6.  It supports the Java Database
Connectivity (JDBC) 4.2 API, and implements the X DevAPI.

This release includes the following new features and changes, also
described in more detail on

https://dev.mysql.com/doc/relnotes/connector-j/8.0/en/news-8-0-20.html

As always, we recommend that you check the "CHANGES" file in the
download archive to be aware of changes in behavior that might affect
your application.

To download MySQL Connector/J 8.0.20 GA, see the "General Availability
(GA) Releases" tab at http://dev.mysql.com/downloads/connector/j/

Enjoy!

Changes in MySQL Connector/J 8.0.20 (2020-04-27, General Availability)



     * Functionality Added or Changed

     * Bugs Fixed

Functionality Added or Changed


      * X DevAPI: Connector/J now supports data compression for X
       Protocol connections
       ( https://dev.mysql.com/doc/refman/8.0/en/x-plugin-connection-compression.html ). 
       See Connection Compression Using X DevAPI
       ( https://dev.mysql.com/doc/connector-j/8.0/en/connector-j-connection-compression-xdevapi.html ) 
       for details.

     * A new method, getElapsedTime(), has been added to
       Connector/J 's implementation of the Statement interface,
       to expose the elapsed time for a query. Thanks to Matti
       Sillanpää for contributing the code. (Bug #30570249, Bug
       #97714)

Bugs Fixed

      * When a custom Calendar was used in the setDate method for
       a PreparedStatement, it was being used by subsequent
       calls of the same method that did not use the same
       calendar, resulting in the wrong date being set. It was
       because the SimpleDateFormat object created internally
       with the custom calendar was cached and reused. With this
       fix, the object is no longer cached. (Bug #30877755)

     * Setting the connection property clientInfoProvider
       without using the fully qualified class name for
       ClientInfoProviderSP caused a NullPointerException. This
       was due to some wrong exception handling, which has been
       corrected by this fix. (Bug #30832513)

     * Authentication failed when a client tried to connect to a
       server that used Windows Authentication Plugin and the
       Kerberos protocol. It was because the implementation of
       the NativeAuthenticationProvider class by Connector/J did
       not interact correctly with a custom-made Kerberos
       authentication plugin, and this patch fixes the issue.
       (Bug #30805426)

     * Methods from the ResultSetUtil class are no longer used
       in Connector/J 8.0.20; the class has therefore been
       removed. (Bug #30636056)

     * A NullPointerException was returned when the connection
       had cacheResultSetMetadata=true and a query containing
       any SET statements was executed. This fix corrects the
       issue by adding the missing variable assignment, and also
       a null check. (Bug #30584907, Bug #97757)

     * A DataConversionException was thrown when an application
       tried to store a string starting with "d." [d was any
       digit] into a VARCHAR column. It was due to a parsing
       error in the AbstractNumericValueFactory, which has been
       fixed by this patch. Thanks to Nick Pollett for
       contributing the code. (Bug #30570721, Bug #97724)

     * When creating a Statement, the specification for the
       resultSetType parameter was not honored, so that the
       ResultSet type was always set to
       ResultSet.TYPE_FORWARD_ONLY. With this fix, the
       resultSetType parameter is now honored. Also, type
       validation has been added so that calling the methods
       beforeFirst, afterLast, first, last, absolute, relative,
       or previous results in an exception if the ResultSet type
       is ResultSet.TYPE_FORWARD_ONLY. (Bug #30474158)

     * When a Calendar was not used, a java.sql.Date value could
       not always be stored into and then retrieved from a MySQL
       server consistently. It was because Connector/J always
       converted a Date value to the server's time zone when
       storing it on the server as a MySQL DATE; but since a
       MySQL DATE does not have any time value, the hour,
       minute, and second parts of the original date was
       effectively lost. If the converted value is one day ahead
       of or behind the original value, when the value was
       retrieved through Connector/J and converted back to the
       local time zone, there was no time value for adjusting
       the date back to its original value, resulting in a
       one-day error. With this fix, any Date value is converted
       to MySQL DATE value using the JVM's time zone, so that
       the value is always consistent when being stored and then
       read back.
       Also, the cacheDefaultTimezone connection property,
       previously removed from Connector/J 8.0, has now been
       restored so that when it is set to false, Connector/J
       becomes aware of the time zone changes of the JVM during
       runtime and converts dates with the updated time zone.
       (Bug #28125069, Bug #91112)

On Behalf of MySQL Release Engineering Team,
Surabhi Bhat

Options: ReplyQuote


Subject
Views
Written By
Posted
MySQL Connector/J 8.0.20 has been released
1017
April 27, 2020 10:52AM


Sorry, you can't reply to this topic. It has been closed.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.