MySQL Connector/J 5.1.44 has been released

Dear MySQL Users,

MySQL Connector/J 5.1.44, a maintenance release of the production 5.1
branch has been released. Connector/J is the Type-IV pure-Java JDBC
driver for MySQL.

MySQL Connector Java is available in source and binary form from the
Connector/J download pages at
and mirror sites as well as Maven-2 repositories.

MySQL Connector Java (Commercial) is already available for download on the
My Oracle Support (MOS) website. This release will be available on eDelivery
(OSDC) in next month’s upload cycle.

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.

MySQL Connector/J 5.1.44 includes the following general bug fixes and
improvements, also available in more detail on

Changes in MySQL Connector/J 5.1.44 (2017-08-30)

Version 5.1.44 is a maintenance release of the production 5.1
branch. It is suitable for use with MySQL Server versions
5.5, 5.6, and 5.7. It supports the Java Database Connectivity
(JDBC) 4.2 API.

Functionality Added or Changed

* A new connection property, enabledTLSProtocols, can now
be used to override the default restrictions on the TLS
versions to be used for connections, which are determined
by the version of the MySQL Server that is being
connected to. By providing a comma-separated list of
values to this option (for example,
“TLSv1,TLSv1.1,TLSv1.2”) users can, for example, prevent
connections from using older TLS version, or allow
connections to use TLS versions only supported by a
user-compiled MySQL Server. See the entry for the new
property in Driver/Datasource Class Names, URL Syntax and
Configuration Properties for Connector/J
reference-configuration-properties.html) for details.
Thanks to Todd Farmer for contributing the code. (Bug

Bugs Fixed

* Important Change: Following the changes in MySQL Server
8.0.3, the system variables tx_isolation and tx_read_only
have been replaced with transaction_isolation and
transaction_read_only in the code of Connector/J. Users
should update Connector/J to this latest release in order
to connect to MySQL 8.0.3. They should also make the same
adjustments to their own applications if they use the old
variables in their codes. (Bug #26440544)

* When using cached server-side prepared statements, a
memory leak occurred as references to opened statements
were being kept while the statements were being decached;
it happened when either the close() method has been
called twice on a statement, or when there were
conflicting cache entries for a statement and the older
entry had not been closed and removed from the opened
statement list. This fix makes sure the statements are
properly closed in both cases. Thanks to Eduard Gurskiy
for contributing to the fix. (Bug #26633984, Bug #87429)

* The regression test for Bug#63800 failed because the
default value of the system variable
explicit_defaults_for_timestamp of MySQL Server has been
changed since release 8.0.2. The test has been adjusted
to take the change into consideration. (Bug #26501245)

On Behalf of the MySQL/ORACLE RE Team,
-Sreedhar S

MySQL Connector/NET 6.10.3 rc has been released

Dear MySQL users,

MySQL Connector/Net 6.10.3 rc is the fourth release which supports
Scaffold-DbContext, that enables the creation of corresponding model
classes from an existing database that are compatible with Entity
Framework (EF) Core 1.1.

To download MySQL Connector/Net 6.10.3 rc, see the “Development
Releases” tab at

Changes in MySQL Connector/Net 6.10.3 (2017-08-18, Release

   Known limitation of this release:

   The use of the SSL protocol is restricted to TCP connections.
   Connections using Unix sockets, named pipes, and shared memory do not
   support SSL mode.

   Functionality Added or Changed

     * The following methods are available for use with EF Core
       in asynchronous command and connection operations:

          + Microsoft.EntityFrameworkCore.DbContext.AddAsync

          + Microsoft.EntityFrameworkCore.DbContext.AddRangeAsync

          + Microsoft.EntityFrameworkCore.DbContext.FindAsync

          + Microsoft.EntityFrameworkCore.DbContext.SaveChangesAsync

          + Microsoft.EntityFrameworkCore.Infrastructure.

          + Microsoft.EntityFrameworkCore.Infrastructure.

          + Microsoft.EntityFrameworkCore.DbContext.ToListAsync

     * Support for connections using Unix sockets was extended
       to include MySQL servers deployed on the Linux host operating
       system in .NET Core scenarios. To specify a Unix socket
       connection, set the value of the Server connection-string option
       to the path of the socket file and the Protocol option to unix.
       For example:

     * The AutoEnlist and IncludeSecurityAsserts
       connection-string options are not appropriate for use by
       applications that target .NET Core and now return an error when

     * EF Core: Support for explicit loading was added. Explicit
       loading is an object-relational mapper (O/RM) pattern introduced
       in EF Core 1.1.0, which enables .NET developers to explicitly
       load related data from the database at a later time.

     * EF Core: Support for scaffolding a DbContext from
       multiple databases was added. With multiple databases (or schemas
       of tables) specified, the resulting entity classes are created
       within a single context.

       EF Core CLI usage example:
       dotnet ef dbcontext scaffold "connection-string"
       MySql.Data.EntityFrameworkCore --schema world --schema sakila

       Package Manager Console (Visual Studio) usage example:
       Scaffold-DbContext "connection-string"
       MySql.Data.EntityFrameworkCore -Schemas world,sakila

     * The following connection-string options are not currently
       supported for use by applications that target .NET Core and now
       return an error when used:

          + SharedMemoryName

          + IntegratedSecurity

          + PipeName

          + Logging

          + UseUsageAdvisor

          + UsePerformanceMonitor

          + InteractiveSession

          + Replication

   Bugs Fixed

     * EF Core: Some methods in the DbContext class were not
       supported for use with asynchronous operations. (Bug #26448321,
       Bug #84814) 

Nuget packages are available at:

Enjoy and thanks for the support!

On behalf of the MySQL Release Team,
Nawaz Nazeer Ahamed

MySQL Connector/Python 2.1.7 GA has been released

Dear MySQL users,

MySQL Connector/Python 2.1.7 GA is a fifth GA version of 2.1 release series of the pure Python database driver for MySQL. It can be used for production environments.

MySQL Connector/Python version 2.1.7 GA is compatible with MySQL Server versions 5.5 and greater. Python 2.6 and greater as well as Python 3.4 and greater are supported. Python 2.4, 2.5, and 3.1, 3.2, 3.3 are not supported.

MySQL Connector/Python 2.1.7 is available for download from: MySQL Connector/Python 2.1.7 (Commercial) will be available for download on the My Oracle Support (MOS) website. This release will be available on eDelivery (OSDC) in next month’s upload cycle.

The ChangeLog file included in the distribution contains a brief summary of changes in MySQL Connector/Python 2.1.7. For a more complete list of changes, see below or online at:


Changes in MySQL Connector/Python 2.1.7 (2017-08-18, General Availability)

 * Functionality Added or Changed

 * Bugs Fixed

   Functionality Added or Changed

 * Connector/Python is now compatible with Django 1.11.
   Thanks to Brian Tyndall for the patch for some of the
   work. (Bug #25965922, Bug #86105, Bug #26257499,

 * Connector/Python now attempts to connect using TLS by
   default if the server supports secure connections. 

   Bugs Fixed

 * Prepared statements did not work with a MySQL 8.0 server.
   (Bug #26376334)

 * With a connection character set of utf8mb4, multiple-row
   insert operations failed with an error of LookupError:
   unknown encoding: utf8mb4. (Bug #24659561, Bug #82948)

 * Creating a Connection instance with use_pure=True could
   lead to the underlying socket not being closed if the
   user name or password were invalid. Thanks to Vilnis
   Termanis for the patch. (Bug #24342757, Bug #82324)

 * For cursors created with named_tuple=True,
   MySQLCursorNamedTuple objects could leak memory. Thanks
   to Piotr Jurkiewicz for the patch on which this fix was
   based. (Bug #22880163, Bug #80621)

 * The C Extension leaked memory if used to execute INSERT
   statements that inserted Unicode strings. (Bug #22825962,
   Bug #79887)

 * The escape_string() method leaked memory. (Bug #22810810,
   Bug #79903)

 * With Python 2.x, for a call to encode('utf8') on a
   bytestring that was serialized from unicode, Python
   attempted to decode the string using the 'ascii' codec
   and encode it back using 'utf8'. The result was encoding
   failure for bytestrings that contain non-ASCII
   characters. (Bug #22564149, Bug #79993)

The source distribution includes the manual in various formats under
the docs/ folder.

Reporting Bugs
We welcome and appreciate your feedback and bug reports:

On Behalf of the MySQL/ORACLE RE Team,
Gipson Pulla