This release fixes bugs since 6.2.0.
MySqlParameter class now has a property
PossibleValues. This property is NULL
unless the parameter is created by
Further, it will be NULL unless the parameter is of type enum or
set - in this case it will be a list of strings that are the
possible values for the column. This feature is designed as an
aid to the developer.
Starting with MySQL Connector/Net 6.2, there is a background job that runs every three minutes and removes connections from pool that have been idle (unused) for more than three minutes. The pool cleanup frees resources on both client and server side. This is because on the client side every connection uses a socket, and on the server side every connection uses a socket and a thread.
Prior to this change, connections were never removed from the pool, and the pool always contained the peak number of open connections. For example, a web application that peaked at 1000 concurrent database connections would consume 1000 threads and 1000 open sockets at the server, without ever freeing up those resources from the connection pool.
MySQL Connector/Net now supports the processing of certificates when connecting to an SSL-enabled MySQL Server. For further information see the connection string option SSL Mode in the section Connector/Net Connection String Options Reference and the tutorial Tutorial: Using SSL with MySQL Connector/Net.
Prior to MySQL Connector/Net 6.2,
MySqlCommand.CommandTimeout included user
processing time, that is processing time not related to direct
use of the connector. Timeout was implemented through a .NET
Timer, that triggered after
MySQL Connector/Net 6.2 introduced timeouts that are aligned with how
This property is the cumulative timeout for all network reads
and writes during command execution or processing of the
results. A timeout can still occur in the
MySqlReader.Read method after the first row
is returned, and does not include user processing time, only IO
Further details on this can be found in the relevant Microsoft documentation.
MySqlCommand was not typesafe. To
MySqlCommand it was necessary to do:
MySqlCommand clone = (MySqlCommand)((ICloneable)comm).Clone();
MySQL Connector/Net was changed so that it was possible to do:
MySqlCommand clone = comm.Clone();
When used, the
Encrypt connection string
option caused a “Keyword not supported” exception
to be generated.
This option is in fact obsolete, and the option SSL Mode should
be used instead. Although the
has been fixed so that it does not generate an exception, it
will be removed completely in version 6.4.
When building the
MySql.Data project with
.NET Framework 3.5 installed, the following build output was
Project file contains ToolsVersion="4.0", which is not supported by this version of MSBuild. Treating the project as if it had ToolsVersion="3.5".
The project had been created using the .NET Framework 4.0, which was beta, instead of using the 3.5 framework. (Bug #48271)
It was not possible to retrieve a value from a MySQL server
table, if the value was larger than that supported by the .NET
MySQL Connector/Net was changed to expose the
type, along with the supporting method
An entity model created from a schema containing a table with a
column of type
UNSIGNED BIGINT and a view of
the table did not behave correctly. When an entity was created
and mapped to the view, the column that was of type
UNSIGNED BIGINT was displayed as
MySQL Connector/Net session support did not work with MySQL Server versions
prior to 5.0, as the Session Provider used a call to
TIMESTAMPDIFF, which was not available on
servers prior to 5.0.