MySQL Connector/NET has been changed to include MySqlDataReader.GetFieldType(string columnname). Further, MySqlDataReader.GetOrdinal() now includes the name of the column in the exception if the column is not found. (Bug#47467)

A non-terminated string in SQL threw a CLR exception rather than a syntax exception. (Bug#51788)

When calling ExecuteNonQuery on a command object, the following exception occurred:

Index and length must refer to a location within the string.
Parameter name: length

(Bug#51610)

Specifying a connection string where an option had no value generated an error, rather than the value being set to the default. For example, a connection string such as the following would result in an error:

server=localhost;user=root;compress=;database=test;port=3306;password=123456;

(Bug#51209)

The method Command.TrimSemicolons used StringBuilder, and therefore allocated memory for the query even if it did not need to be trimmed. This led to excessive memory consumption when executing a number of large queries. (Bug#51149)

MySqlCommand.Parameters.Clear() did not work. (Bug#50444)

When the MySqlScript.execute() method was called, the following exception was generated:

InvalidOperationException : The CommandText property has not been properly initialized.

(Bug#50344)

When using the Compact Framework the following exception occurred when attempting to connect to a MySQL Server:

System.InvalidOperationException was unhandled
  Message="Timeouts are not supported on this stream."

(Bug#50321)

Binary Columns were not displayed in the Query Builder of Visual Studio. (Bug#50171)

When the UpdateBatchSize property was set to a value greater than 1, only the first row was applied to the database. (Bug#50123)

When using table per type inheritance and listing the contents of the parent table, the result of the query was a list of child objects, even though there was no related child record with the same parent Id. (Bug#49850)

MySqlDataReader.GetUInt64 returned an incorrect value when reading a BIGINT UNSIGNED column containing a value greater than 2147483647. (Bug#49794)

A FormatException was generated when an empty string was returned from a stored function. (Bug#49642)

When trying to create stored procedures from a SQL script, a MySqlException was thrown when attempting to redefine the DELIMITER:

        MySql.Data.MySqlClient.MySqlException was unhandled
        Message="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 'DELIMITER' at line 1"
        Source="MySql.Data"
        ErrorCode=-2147467259
        Number=1064
        StackTrace:
        à MySql.Data.MySqlClient.MySqlStream.ReadPacket()
        à MySql.Data.MySqlClient.NativeDriver.ReadResult(UInt64& affectedRows, Int64&
        lastInsertId)
        à MySql.Data.MySqlClient.MySqlDataReader.GetResultSet()
        à MySql.Data.MySqlClient.MySqlDataReader.NextResult()
        à MySql.Data.MySqlClient.MySqlCommand.ExecuteReader(CommandBehavior behavior)
        à MySql.Data.MySqlClient.MySqlCommand.ExecuteReader()
        à MySql.Data.MySqlClient.MySqlCommand.ExecuteNonQuery()
      à MySql.Data.MySqlClient.MySqlScript.Execute()

Note: The MySqlScript class has been fixed to support the delimiter statement as it is found in SQL scripts. (Bug#46429)

Calling a User Defined Function using Entity SQL in the Entity Framework caused a NullReferenceException. (Bug#45277)

A connection string set in web.config could not be reused after Visual Studio 2008 Professional was shut down. It continued working for the existing controls, but did not work for new controls added. (Bug#41629)