MySQL Connector/Python 2.1.6 GA has been released

Dear MySQL users,

MySQL Connector/Python 2.1.6 GA is a fourth 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.6 GA is compatible with MySQL Server
versions 5.5 and greater. Python 2.6 and greater as well as Python 3.3
and greater are supported. Python 2.4, 2.5 and 3.1, 3.2 are not
supported.

MySQL Connector/Python 2.1.6 is available for download from:

http://dev.mysql.com/downloads/connector/python/#downloads

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

http://dev.mysql.com/doc/relnotes/connector-python/en/

Enjoy!

Changes in MySQL Connector/Python 2.1.6 (2017-04-18, General
Availability)

Functionality Added or Changed

* An ssl-cipher option is now supported for specifying the
encryption cipher for secure connections. (Bug #22545879,
Bug #78186)

Bugs Fixed

* Compatibility issues with Django 1.9 were corrected. (Bug
#25726671)

* The fix for Bug #22529828 caused Python 2.7 to be unable
to insert binary data. (Bug #25589496, Bug #85100)
References: This issue is a regression of: Bug #22529828.

* Some SQL statements that worked using pure Python failed
with the Connector/Python C Extension enabled. (Bug
#25558885)

* Connector/Python produced no error or warning if the
server certificate was expired. (Bug #25397650)

* If an exception reset the underlying session, connections
in a connection pooled could become unavailable to the
pool. (Bug #25383644, Bug #84476)

* Methods for filtering time and datetime fields were
changed in Django 1.9 from value_to_db_datetime to
adapt_datetimefield_value and from value_to_db_time to
adapt_timefield_value. Proxy methods with the previous
names were added to Connector/Python ensure
compatibility. Thanks to Brian Tyndall for the patch.
(Bug #25349918, Bug #84410)

* Extra encapsulation was removed from the get_constraints
method for the foreign_key parameter. Thanks to Brian
Tyndall for the patch. (Bug #25349912, Bug #84409)

* Connector/Python added support for a database backend API
change introduced in Django 1.9 for the bulk_insert_sql
method. Thanks to Brian Tyndall for the patch. (Bug
#25349897, Bug #84408)

* Loading the world sample database worked using pure
Python but failed with the Connector/Python C Extension
enabled. (Bug #22476689, Bug #79780)

* If the output from the mysql_config –include command
included more than one directory, the C Extension failed
to compile. (Bug #20736339, Bug #76350)

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

MySQL for Visual Studio 1.2.7 has been released

The MySQL Windows Experience Team is proud to announce the release of MySQL for Visual Studio 1.2.7. This is a maintenance release for 1.2.x. It can be used for production environments.

MySQL for Visual Studio is a product that includes all of the Visual Studio integration functionality to create and manage MySQL databases when developing .NET applications.

MySQL for Visual Studio is installed using the MySQL Installer for Windows which comes in 2 versions:

  • Full (352.8 MB) which includes a complete set of MySQL products with their binaries included in the downloaded bundle.
  • Web (1.7 MB – a network install) which will just pull MySQL for Visual Studio over the web and install it when run.

You can download MySQL Installer from our official Downloads page at http://dev.mysql.com/downloads/installer/.

MySQL for Visual Studio can also be downloaded by using the product standalone installer found at http://dev.mysql.com/downloads/windows/visualstudio/.

 

Changes in MySQL for Visual Studio 1.2.7 (2017-04-10)

Functionality Added or Changed

  • Removed Support for Microsoft Visual Studio 2010.
  • Added support for Microsoft Visual Studio 2017.

Bugs Fixed

  • The MySQL Data Export Tool exported data from the wrong
    schema when a second schema was selected and then deselected.
    In addition, all selected schemas were deselected when a single
    schema was deselected. (Bug #25713981)
  • Script files did not accept most keyboard input after the
    file was saved for the first time. (Bug #25713638)

 

What Is New In MySQL for Visual Studio 1.2

  • New MySQL Project Items for creating data views in Windows Forms and ASP.NET MVC web applications.
  • A new option in web configuration tool for the ASP.NET Personalization Provider (this feature requires MySQL Connector/NET 6.9 or newer).
  • A new option in web configuration tool for the ASP.NET Site Map Provider (this feature requires MySQL Connector/NET 6.9 or newer).
  • A new option for the MySQLSimpleMembership provider in the web configuration tool. (This feature requires MySQL Connector/NET or newer).

 

MySQL Windows Forms Project Item
——————————————————————————————-
This Project Item is available on the Add New Item dialog in Visual Studio when adding a new item to an existing project.

The dialog presented to create the MySQL Windows Forms Project Item automates the generation of a Windows Form, representing a view for MySQL data available through an existing Entity Framework’s model entity containing a MySQL table or view. Different view types are available to present the data:

  • Single-column: A form that contains one control by each existing column in the table with navigation controls and that allows CRUD operations.All controls can include validations for numeric and DateTime data types.
  • Grid: A form with a data grid view that contains navigation controls.
  • Master-detail: A form with a single control layout for the Parent table and a data grid view to navigate through child table’s data.

Supported with C# or Visual Basic language. This feature requires Connector/NET 6.7.5, 6.8.3 or 6.9.x.

For more details on the features included check the documentation at: https://dev.mysql.com/doc/connector-net/en/visual-studio-project-items-forms.html

 

MySQL ASP.NET MVC Project Item
——————————————————————————————-
This Project Item is available on the Add New Item dialog in Visual Studio when adding a new item to an existing project.

The dialog presented to create the MySQL ASP.NET MVC Item automates the generation of a controller and its corresponding view, representing a view for MySQL data available through an existing Entity Framework’s model entity containing a MySQL table or view. The MVC versions supported by this wizard are 3 when using Visual Studio 2010 or 2012, and 4 when using Visual Studio 2013 or greater.

The generation of the MVC items is done by creating an Entity Framework data model either with Entity Framework version 5 or 6 depending on the user’s selection.

Supported with C# or Visual Basic language. This feature requires Connector/NET 6.7.5, 6.8.3 or 6.9.x.

For more details on the features included check the documentation at: https://dev.mysql.com/doc/connector-net/en/visual-studio-project-items-mvc.html

 

New option in web configuration tool for the ASP.NET Personalization Provider
——————————————————————————————-
Personalization provider allows to store personalization state-state data regarding the content and layout of Web Parts pages-generated by the Web Parts personalization service using MySQL as a data source. This feature requires Connector/NET 6.9.x or greater.

https://dev.mysql.com/doc/connector-net/en/connector-net-tutorials-web-personalization-provider.html

 

New option in web configuration tool for the ASP.NET Site Map Provider
——————————————————————————————-
Site Map provider allows to show a hierarchical list of links that describe the structure of a site. This feature requires Connector/NET 6.9.x or greater.

http://dev.mysql.com/doc/connector-net/en/connector-net-website-config.html

 

New option in web configuration tool for the ASP.NET Simple Membership provider
——————————————————————————————-
The latest provider added to handle web site membership tasks with ASP.NET. This feature requires Connector/Net 6.9.x or greater.

http://dev.mysql.com/doc/connector-net/en/connector-net-simple-membership-tutorial.html

 

 

Quick links:

Enjoy and thanks for the support!

MySQL Connector/Python 2.2.3 m4 Development Release has been released

MySQL Connector/Python 2.2.3 M4 is the fourth development release of the MySQL Connector Python 2.2 series. This series adds support for the new X DevAPI. The X DevAPI enables application developers to write code that combines the strengths of the relational and document models using a modern, NoSQL-like syntax that does not assume previous experience writing traditional SQL.

To learn more about how to write applications using the X DevAPI, see http://dev.mysql.com/doc/x-devapi-userguide/en/. For more information about how the X DevAPI is implemented in MySQL Connector/Python, and its usage, see http://dev.mysql.com/doc/dev/connector-python.

Please note that the X DevAPI requires MySQL Server version 5.7.12 or higher with the X Plugin enabled. For general documentation about how to get started using MySQL as a document store, see http://dev.mysql.com/doc/refman/5.7/en/document-store.html.

To download MySQL Connector/Python 2.2.3 M4, see the “Development Releases” tab at http://dev.mysql.com/downloads/connector/python/

Enjoy!

Changes in MySQL Connector/Python 2.2.3 (2017-03-22, Milestone 3)

Functionality Added or Changed

* Connector/Python now supports IPv6 target hosts in X DevAPI connection strings.

Bugs Fixed

* The defined_as(statement) method used to create views did not permit a SelectStatement object argument (generated by Table.select()). (Bug #25614860)

* The SelectStatement object returned by Table.select() failed to provide the order_by() method. (Bug #25519251)

* The pure Python implemention of Protobuf has been replaced by a C++ extension. This enables Connector/Python to support Python 2 and 3 as well as Protobuf 2 and 3. (Bug #25209469)

* import mysqlx caused an error with Python 2.6 on Solaris and EL6 platforms. (Bug #24578507)

* The error message for get_session() failure was incorrect. (Bug #23636962)

* The Collection.find() method failed to work with the LIKE operator or aggregate functions. The Collection.find() method failed to work with several
operators. Support was added for these operators:

+ Nullary Operators: *

+ Unary Operators: !, NOT, +, -, ~

+ Binary Operators: AND, &&, OR, ||, XOR, <>, ^, IS NOT, NOT REGEXP, NOT LIKE, CAST, NOT IN

+ Ternary Operators: NOT BETWEEN

In addition, arrow notation to access JSON columns is now functional (for example, schema.table.column->’$.document field’). (Bug #23567724, Bug #23568207, Bug #25436568, Bug #84585)

Documentation
——————–

Online: http://dev.mysql.com/doc/connector-python/en/index.html
The source distribution includes the manual in various formats under the docs/ folder.

Reporting Bugs
——————–

We welcome and appreciate your feedback and bug reports:
http://bugs.mysql.com/

On Behalf of the MySQL/ORACLE RE Team,
Piotr Obrzut

MySQL Connector/C++ 2.0.4 m2 has been released

MySQL Connector/C++ 2.0.4 is the next development milestone of the MySQL

Connector/C++ 2.0 series. Connector/C++ 2.0 can be used to access MySQL
implementing Document Store or in a traditional way, using SQL queries. It
allows writing both C++ applications using X DevAPI or plain C applications
using XAPI.

To learn more about how to write applications using X DevAPI, see X
DevAPI User Guide (http://dev.mysql.com/doc/x-devapi-userguide/en/) and X
DevAPI reference at
https://dev.mysql.com/doc/dev/connector-cpp/devapi_ref.html. For more
information about using plain C XAPI see XAPI reference at
http://dev.mysql.com/doc/dev/connector-cpp/xapi_ref.html. For generic
information on using Connector/C++ 2.0, see
http://dev.mysql.com/doc/dev/connector-cpp/.

Note

Connector/C++ 2.0 requires MySQL Server version 5.7.12 or higher
with X Plugin enabled. For general documentation about how to get
started using MySQL as a document store, see Using MySQL as a Document
Store (http://dev.mysql.com/doc/refman/5.7/en/document-store.html).

To download MySQL Connector/C++ 2.0.4, see the “Development Releases”
tab at http://dev.mysql.com/downloads/connector/cpp/

Changes in MySQL Connector/C++ 2.0.4 (2017-03-21, Development
Milestone)

Functionality Added or Changed

  • Support was added for secure sessions over TLS
    connections. A secure session can be requested either via
    the ssl-enable and ssl-ca options of a connection string,
    or using explicit session creation options. For X DevAPI
    session settings, see http://dev.mysql.com/doc/dev/connector-cpp/classmysqlx_1_1_session_settings.html.
    For XAPI session settings, see
    http://dev.mysql.com/doc/dev/connector-cpp/group__xapi.html
    (check the documentation for enum mysqlx_opt_type_t).
  • The format of document ID values generated when adding
    documents to a collation has changed. It is still a
    string of 32 hexadecimal digits based on UUID, but the
    order of digits was changed to match the requirement of a
    stable ID prefix.
  • The X DevAPI Schema object now supports methods for view
    manipulation: createView(), alterView(), and dropView().
    XAPI now contains functions that implement similar
    functionality: mysqlx_view_create(),
    mysqlx_view_replace(), mysqlx_view_modify(), and
    (implemented previously) mysqlx_view_drop().
    As with other XAPI operations, there are functions that
    create a statement handle without executing it:
    mysqlx_view_create_new(), mysqlx_view_replace_new(), and
    mysqlx_view_modify_new().
    These XAPI functions modify view DDL statements before
    execution: mysqlx_set_view_algorithm(),
    mysqlx_set_view_security(),
    mysqlx_set_view_check_option(),
    mysqlx_set_view_definer(), and mysqlx_set_view_columns().
  • Connector/C++ now supports IPv6 target hosts in
    connection strings and when creating sessions using other
    methods.

Bugs Fixed

  • When rList is an empty list, table.insert().rows(rList)
    caused a segmentation fault. (Bug #25515964)

On Behalf of the MySQL/ORACLE RE Team

MySQL Connector/NET 7.0.7 m6 development has been released

MySQL Connector/Net 7.0.7 is the fourth development release that expands cross-platform support to Linux and OS X when using Microsoft’s .NET Core framework. Now,
.NET developers can use the X DevAPI with .NET Core and Entity Framework Core
(EF Core) 1.0 to create server applications that run on Windows, Linux and OS X.
We are very excited about this change and really look forward to your feedback on it!

MySQL Connector/Net 7.0.7 is also the sixth development release of MySQL Connector/Net to add support for the new X DevAPI. The X DevAPI enables
application developers to write code that combines the strengths of the
relational and document models using a modern, NoSQL-like syntax that
does not assume previous experience writing traditional SQL.

To learn more about how to write applications using the X DevAPI, see
http://dev.mysql.com/doc/x-devapi-userguide/en/index.html. For more
information about how the X DevAPI is implemented in Connector/Net, see
http://dev.mysql.com/doc/dev/connector-net.

Note

The X DevAPI requires at least MySQL Server version 5.7.12 or higher with
the X Plugin enabled. For general documentation about how to get started
using MySQL as a document store, see
http://dev.mysql.com/doc/refman/5.7/en/document-store.html.

To download MySQL Connector/Net 7.0.7 M6, see the “Development
Releases” tab at http://dev.mysql.com/downloads/connector/net/

Functionality Added or Changed

  • X DevAPI: Added support for Internet Protocol version 6 (IPv6) addresses. Host names can now resolve as IPv4 or IPv6 addresses.
  • X DevAPI: Connection string syntax is now identical to the URI scheme, which provides a cross-product syntax for defining the connection data to establish a session.
  • X DevAPI: Added new methods to the Schema class to create, alter, and drop views. Usage notes include:
    • Views created with the Schema.CreateView().DefinedAs() method chain are
      supported for use with the table Select method, but are not supported with the collection Find method.
    • A collection view created in the database by some mechanism other than the CreateView method is not defined as a view by Table.IsView.
    • Query objects assigned to a view with the CreateView method are static, even when the underlying query changes.

Nuget

Packages are available at:

https://www.nuget.org/packages/MySql.Data/7.0.7-m6
https://www.nuget.org/packages/MySql.Web/7.0.7-m6
https://www.nuget.org/packages/MySql.Data.Entity/7.0.7-m6
https://www.nuget.org/packages/MySql.Data.EntityFrameworkCore/7.0.7-m6

Enjoy and thanks for the support!

MySQL/Oracle Release Engineering Team

MySQL Connector/Java 6.0.6 m5 has been released

Link

Dear MySQL users,

MySQL Connector/J 6.0.6 m5 Development Release is a developer milestone
release for the 6.0.x series.
This release includes the following new features and changes, also described
in more detail on
https://dev.mysql.com/doc/relnotes/connector-j/6.0/en/news-6-0-6.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 6.0.6 m5, see the “Development
Releases” tab at http://dev.mysql.com/downloads/connector/j/

Enjoy!

Changes in MySQL Connector/J 6.0.6 (2017-03-10, Milestone 5)

Version 6.0.6 Milestone is the fifth development release of
the 6.0 branch of MySQL Connector/J, providing an insight
into upcoming features. 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

* Bugs Fixed

Functionality Added or Changed

* X DevAPI: The getPluginVersion() method has been removed
from Connector/J, as it is no longer supported by the X
Protocol. (Bug #25056803)

* IPv6 host addresses are now supported for connections
using the X Protocol.

* X DevAPI: The following new connection options have been
added for SSL/TLS configuration:

+ xdevapi.ssl-enable

+ xdevapi.ssl-truststore

+ xdevapi.ssl-verify-server-certificate
See Configuration Properties

http://dev.mysql.com/doc/connector-j/6.0/en/connector-j-reference-configuration-properties.html

for details.

* Connector/J now supports the new character set collations
implemented in MySQL Server 8.0. See Unicode Character
Sets
http://dev.mysql.com/doc/refman/5.7/en/charset-unicode-sets.html
for details.

* X DevAPI: DDL for views are now supported by the new
methods createView(), dropView(), and alterView().
However, the functions do not support partitioning in an
InnoDB cluster or sharding.

* X DevAPI: The Connector/J X Dev API has been reorganized:

+ All interfaces for public usage have been moved to
the com.mysql.cj.api.xdevapi package, and their
implementation classes to com.mysql.cj.xdevapi.

+ All Connector/J internal interfaces have been moved
to the com.mysql.cj.api.x.core and
com.mysql.cj.api.x.io packages, and their
implementation classes to com.mysql.cj.x.core and
com.mysql.cj.x.io.

+ Protobuf generated classes have been moved to the
com.mysql.cj.x.protobuf package.

+ The MysqlxSessionFactory has been renamed
XSessionFactory.

Bugs Fixed

* When Connector/J was reading a TIMESTAMP value into an
instance of a JSR-310 data type, the reading was wrong
when the time did not exist in the local time zone of the
JVM due to a time change for Daylight Saving Time. It was
because Connector/J created first a java.sql.Timestamp
instance (which used the JVM’s time zone) for the value
and then converted it to, for example,
java.time.LocalDateTime. With this fix, a JSR-310 object
is created directly to avoid the conversion. (Bug
#24658016, Bug #82964)

* Query executions using prepared statements failed with
the error “Unknown ProtocolEntity class null” when the
connection property useCursorFetch was set to true. (Bug
#24527173)

* When server-side prepared statements were used, updates
to result sets failed in errors. (Bug #24525461)

* The getString() method returned wrong millisecond values
for the TIMESTAMP data type. (Bug #24512766, Bug #82707)

* Updates to a document object of the Dbdoc type failed
when the document contained an array. (Bug #24471057)

* The method isNumberSigned() returned true for columns of
type VARCHAR, which was wrong as it should return false
for any non-numeric columns, according to the JDBC
Specification. The behavior has now been corrected. (Bug
#24350526)

* An IllegalArgumentException was thrown when lenient was
false for a Calendar object and the hours, minutes, and
seconds explicitly set via the Calendar constructor did
not match the values resulted from the timezone
conversion of the Calendar object’s date value. (Bug
#23702040, Bug #82005)

* X DevAPI: The getLastDocumentIds() method only reported
document IDs specified by users, but not those generated
by Connector/J. With this fix, all IDs are now reported.
(Bug #23519211)

* A connection failed with IllegalStateException:
TrustManagerFactoryImpl is not initialized after
Connector/J set javax.net.ssl.trustStore. (Bug #23510894)

* A NullPointerException was thrown when a NULL object of
any of the classes defined in the java.time package was
retried by the ResultSet.getObject() method. (Bug
#23188159, Bug #81202)

* The getType() method returned errors on columns of YEAR
and DATETIME data types. (Bug #22931277)

On Behalf of MySQL/ORACLE RE Team
Gipson Pulla

MySQL Connector/NodeJS 1.0.6 M5 has been released

MySQL Connector/Node.js is a new Node.js driver for use with the X DevAPI. This release, v1.0.6 M5, is the fourth development release of the MySQL Connector/Node.js 1.0 series.

The X DevAPI enables application developers to write code that combines the strengths of the relational and document models using a modern, NoSQL-like syntax that does not assume previous experience writing traditional SQL.

MySQL Connector/Node.js can be downloaded through npm (see https://www.npmjs.com/package/@mysql/xdevapi for details) or from https://dev.mysql.com/downloads/connector/nodejs/.

To learn more about how to write applications using the X DevAPI, see http://dev.mysql.com/doc/x-devapi-userguide/en/. For more information about how the X DevAPI is implemented in MySQL Connector/Node.js, and its usage, see http://dev.mysql.com/doc/dev/connector-nodejs/.

Note

Please note that the X DevAPI requires at least MySQL Server version 5.7.12 or higher with the X Plugin enabled. For general documentation about how to get started using MySQL as a document store, see http://dev.mysql.com/doc/refman/5.7/en/document-store.html.

Functionality Added or Changed

  • Added support for validating the server certificate with
    a given CA and/or CRL.
  • Added support for creating TLS sessions with a URI or
    connection string.
  • Added support for creating IPv6 sessions with a URI or
    connection string.
  • Added support for single array or multiple argument
    function calls on the public API.

Bugs Fixed

  • Fixed issues with collection.bind(). (Bug #23236379)
  • Fixed parsing issues on URI and connection string
    corner-cases.
  • Updated behavior of collection.add([]) to avoid confusing
    exceptions.

Enjoy and thanks for the support!

On behalf of the MySQL/Oracle Release Engineering Team
Lars Tangvald

MySQL Connector/J 5.1.41 has been released

Dear MySQL Users,

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

Version 5.1.41 is suitable for use with many MySQL server versions,
including 4.1, 5.0, 5.1, 5.4 and 5.5.

MySQL Connector Java is available in source and binary form from the
Connector/J download pages at
http://dev.mysql.com/downloads/connector/j/5.1.html
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.41 includes the following general bug fixes and
improvements, also available in more detail on
http://dev.mysql.com/doc/relnotes/connector-j/en/news-5-1-41.html

Changes in MySQL Connector/J 5.1.41 (2017-02-28)

Version 5.1.41 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.

Bugs Fixed

* Connections failed with MySQLSyntaxErrorException:
Unknown character set when
connectionCollation=ISO-8859-13. This was due to a wrong
logic in Connector/J’s internal charset mapping, which
has now been fixed. (Bug #25504578)

* When loading classes through some external class loaders,
com.mysql.jdbc.Util threw an NoClassDefFoundError. This
was caused by Class.getPackage() returning null when some
external class loaders were used. This fix replaces those
calls of Class.getPackage() with calls of the new method
Class.getName(), which return package names that are
extracted from the fully-qualified class names. (Bug
#25048543, Bug #83052)

* In the manifest for the Connector/J JAR file, the
Import-Package directive specified version numbers for
the javax.net.ssl package. The specification was
unnecessary, and it caused the configuration of an SSL
connection to a MySQL server to fail in an OSGi
environment. The version requirement has now been
removed. (Bug #24942672, Bug #82826)

* In a Fabric setup, when multiple threads required to have
hashes computed, an ArrayIndexOutOfBoundsException might
be thrown from inside HashShardMapping. This fix prevents
the issue by having
HashShardMapping.getShardIndexForKey() synchronized. (Bug
#24289730, Bug #82203)

* When the configuration property cacheResultSetMetadata
was set to true, a ping query using a PreparedStatement
failed with a NullPointerException. This fix moves the
ping query to an earlier stage of the statement
execution, which prevents the exception. (Bug #23535001,
Bug #81706)

* The setFabricShardTable() method failed to parse
qualified table names (in the format of
database_name.table_name), which causes SQLExceptions to
be thrown. (Bug #23264511, Bug #81108)

* A race condition occurred when a call of
Connection.setNetworkTimeout() was followed closely by a
call of Connection.close(), and a NullPointerException
might result if the connection was closed before the
executor supplied to setNetworkTimeout() was able to set
the timeout, as the executor would run into a null
mysqlConnection object. This fix removed the race
condition. (Bug #21181249, Bug #75615)

* With the connection properties
cacheServerConfiguration=true and
elideSetAutoCommits=true, any new connection to the
server obtained after the first connection was
established had the variable autoCommit equaled false,
even if the value of the variable was true on the server.
That was because the value of autoCommit was not properly
initialized when a new connection was established, and
this fix corrects that.
Also, since release 5.1.41, the functionality of the
property elideSetAutoCommits has been disabled due to
Bug# 66884. Any value given for the property is now
ignored by Connector/J. (Bug #17756825, Bug #70785)

* When using Tomcat and a web application that utilized
Connector/J was down, Tomcat was unable to stop the
AbandonedConnectionCleanupThread started internally by
Connector/J, leading to multiple instances of the thread
when the web application was restarted; or, Tomcat was
able to stop the thread but unable to restart it on
reload of the web application. Different combinations of
Tomcat’s default settings, usage of Tomcat’s
ServletContextListener feature, and locations of the
Connector/J jar could result in the undesired behaviors,
as well as warning messages in the Tomcat error log
saying it was unable to stop the thread and a memory leak
was likely.
The implementation of AbandonedConnectionCleanupThread
has now been improved, so that there are now four ways
for developers to deal with the situation:

+ When the default Tomcat configuration is used and
the Connector/J jar is put into a local library
directory, the new built-in application detector in
Connector/J now detects the stopping of the web
application within 5 seconds and kills
AbandonedConnectionCleanupThread. Any unnecessary
warnings about the thread being unstoppable are also
avoided. If the Connector/J jar is put into a global
library directory, the thread is left running until
the JVM is unloaded.

+ When Tomcat’s context is configured with the
attribute clearReferencesStopThreads=”true”, Tomcat
is going to stop all spawned threads when the
application stops unless Connector/J is being shared
with other web applications, in which case
Connector/J is now protected against an
inappropriate stop by Tomcat; the warning about the
non-stoppable thread is still issued into Tomcat’s
error log.

+ When a ServletContextListener is implemented within
each web application that calls
AbandonedConnectionCleanupThread.checkedShutdown()
on context destruction, Connector/J now, again,
skips this operation if the driver is potentially
shared with other applications. No warning about the
thread being unstoppable is issued to Tomcat’s error
log in this case.

+ When
AbandonedConnectionCleanupThread.uncheckedShutdown()
is called, the AbandonedConnectionCleanupThread is
closed even if Connector/J is shared with other
applications. However, it may not be possible to
restart the thread afterwards.
(Bug #17035755, Bug #69526)
References: See also: Bug #14570236, Bug #16443387.

On Behalf of MySQL/ORACLE RE Team
Gipson Pulla

MySQL Connector/NET 6.10.1 beta has been released

MySQL Connector/Net 6.10.1 beta is the second 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.1 beta, see the “Development Releases” tab at http://dev.mysql.com/downloads/connector/net/

Known limitations of this release

  • The output classes cannot exist prior to using the EF Core database first feature.
  • The target database must have a table with a primary key.
  • The target database cannot contain one or more views.
  • The JSON data exchange format is not supported by the EF Core database first feature.
  • No error message is provided when a table given as input does not exist in the database and a model context is created without any table by the EF Core database first feature.
  • The EF Core database first feature does not support the following data types:
    + BINARY
    + VARBINARY
    + MEDIUMBLOB
    + LONGBLOB
    + SET
    + DATE
    + TIME
    + YEAR
  • DbContext within an application can emit an unhandled exception. Due to this limitation, MySQL Connector/Net 6.9.9 is the preferred version to use with EF6.

Functionality Added or Changed

  • Added database first support, also known as Scaffold-DbContext, which enables the creation of corresponding model classes from an existing database that are compatible with Entity Framework (EF) Core 1.1.

Bugs Fixed

  • EF Core: Using the Contains method in an expression with a variable generated an exception. (Bug #25394204, Bug #84505)
  • EF Core: Using the Skip and Take methods in an assignment generated an exception. (Bug #25382036, Bug #84453)

Nuget

Packages are available at:

https://www.nuget.org/packages/MySql.Data/6.10.1-beta https://www.nuget.org/packages/MySql.Web/6.10.1-beta https://www.nuget.org/packages/MySql.Data.Entity/6.10.1-beta https://www.nuget.org/packages/MySql.Data.EntityFrameworkCore/6.10.1-beta https://www.nuget.org/packages/MySql.Data.EntityFrameworkCore.Design/6.10.1-beta

Enjoy and thanks for the support!

On behalf of the MySQL Release Team,
Nawaz Nazeer Ahamed

MySQL Connector/C 6.1.9 GA has been released

Dear MySQL Users,

A new GA (general availability) version of MySQL Connector/C has
been made available: MySQL Connector/C 6.1.9 GA. The MySQL
Connector/C provides a C API for connecting client applications to
the MySQL Server 5.5 or newer.

You can download the production release at:

http://dev.mysql.com/downloads/connector/c/1.1.html

MySQL Connector C (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.

We have improved the driver since the last GA release. Please see the
documentation and the CHANGES file in the source distribution for a
detailed description of bugs that have been fixed. Bug descriptions are
also listed below.

Enjoy!

======================================================================

Changes in MySQL Connector/C 6.1.9 (2017-01-10, General
Availability)

Security Notes

* OpenSSL is ending support for version 1.0.1 in December
2016; see
https://www.openssl.org/policies/releasestrat.html.
Consequently, Connector/C Commercial builds now use
version 1.0.2 rather than version 1.0.1, and the linked
OpenSSL library for the Connector/C Commercial has been
updated from version 1.0.1 to version 1.0.2j. For a
description of issues fixed in this version, see
https://www.openssl.org/news/vulnerabilities.html.
This change does not affect Oracle-produced MySQL
Community builds of Connector/C, which use the yaSSL
library instead. (Bug #24753384)

* A new MYSQL_OPT_TLS_VERSION option is available for the
mysql_options() C API function to indicate the protocols
permitted by the client for encrypted connections.
For more information, see mysql_options()
(http://dev.mysql.com/doc/refman/5.7/en/mysql-options.html).
(Bug #22932026)

* A new MYSQL_OPT_SSL_MODE option is available for the
mysql_options() C API function to indicate the security
state to use for the connection to the server.
For more information, see mysql_options()
(http://dev.mysql.com/doc/refman/5.7/en/mysql-options.html).
(Bug #22931973)

Functionality Added or Changed

* Previously, Connector/C permitted user names up to a
maximum of 16 characters. Connector/C now permits longer
user names (up to 32 characters) if the server does. (Bug
#22931954)

* Connector/C now includes support for the server GTID
session tracker, introduced in MySQL 5.7.6. This tracker
is exposed through the session_track_gtids system
variable. (Bug #21040741)

* Connector/C now includes support for additional ranges of
server errors, introduced in MySQL 5.7.6. (Bug #21040703)

On Behalf of the MySQL/ORACLE RE Team
Piotr Obrzut