Cloning of MySqlCommand was not typesafe. To clone a 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();
      

(Bug#48460)

When building the MySql.Data project with .NET Framework 3.5 installed, the following build output was displayed:

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)

If MySqlConnection.GetSchema was called for "Indexes" on a table named “b`a`d” as follows:

DataTable schemaPrimaryKeys = connection.GetSchema(
  "Indexes",
  new string[] { null, schemaName, "b`a`d"});

Then the following exception was generated:

You have an error in your SQL syntax; check the manual that corresponds to
your MySQL server version for the right syntax to use near 'a`d`' at line 1

(Bug#48101)

It was not possible to retrieve a value from a MySQL server table, if the value was larger than that supported by the .NET type System.Decimal.

MySQL Connector/NET was changed to expose the MySqlDecimal type, along with the supporting method GetMySqlDecimal. (Bug#48100)

For some character sets such as UTF-8, a CHAR column would sometimes be incorrectly interpreted as a GUID by MySQL Connector/NET.

MySQL Connector/NET was changed so that a column would only be interpreted as a GUID if it had a character length of 36, as opposed to a byte length of 36. (Bug#47985)

When using a BINARY(16) column to represent a GUID and having specified “old guids = true” in the connection string, the values were returned correctly until a null value was encountered in that field. After the null value was encountered a format exception was thrown with the following message:

Guid should contain 32 digits with 4 dashes (xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx).

(Bug#47928)

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 BIGINT. (Bug#47872)

The Session Provider created invalid “session expires” on a random basis.

This was due to the fact that the Session Provider was incorrectly reading from the root web.config, rather than from the application specific web.config. (Bug#47815)

Attempting to build MySQL Connector/NET 6.1 MySQL.Data from source code on Windows failed with the following error:

...\clones\6.1\MySql.Data\Provider\Source\NativeDriver.cs(519,29): error CS0122:
'MySql.Data.MySqlClient.MySqlPacket.MySqlPacket()' is inaccessible due to its protection level

(Bug#47354)

When tables were auto created for the Session State Provider they were set to use the MySQL Server's default collation, rather than the default collation set for the containing database. (Bug#47332)

When loading the MySQLClient-mono.sln file included with the Connector/NET source into Mono Develop, the following error occurred:

/home/tbedford/connector-net-src/6.1/MySQLClient-mono.sln(22):
Unsupported or unrecognized project:
'/home/tbedford/connector-net-src/6.1/Installer/Installer.wixproj'

If the file was modified to remove this problem, then attempting to build the solution generated the following error:

/home/tbedford/connector-net-src/6.1/MySql.Data/Provider/Source/Connection.cs(280,46):
error CS0115: `MySql.Data.MySqlClient.MySqlConnection.DbProviderFactory' is marked as an
override but no suitable property found to override

(Bug#47048)