This release fixes bugs since 6.2.2.
Functionality Added or Changed
MySQL Connector/Net has been changed to include
MySqlDataReader.GetOrdinal() now includes the
name of the column in the exception if the column is not found.
A non-terminated string in SQL threw a CLR exception rather than a syntax exception. (Bug #51788)
ExecuteNonQuery on a command
object, the following exception occurred:
Index and length must refer to a location within the string. Parameter name: length
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:
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
MySqlCommand.Parameters.Clear() did not work.
MySqlScript.execute() method was
called, the following exception was generated:
InvalidOperationException : The CommandText property has not been properly initialized.
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."
Binary Columns were not displayed in the Query Builder of Visual Studio. (Bug #50171)
UpdateBatchSize property was set to
a value greater than 1, only the first row was applied to the
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
UNSIGNED column containing a value greater than
FormatException was generated when an empty
string was returned from a stored function.
When trying to create stored procedures from an SQL script, a
MySqlException was thrown when attempting to
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()
MySqlScript class has been fixed to
support the delimiter statement as it is found in SQL scripts.
Calling a User Defined Function using Entity SQL in the Entity
Framework caused a
A connection string set in
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.