This release fixes bugs since 6.3.0.
Functionality Added or Changed
Connector/Net was not compatible with Visual Studio wizards that used square brackets to delimit symbols.
Connector/Net has been changed to include a new connection
Sql Server mode that supports
use of square brackets to delimit symbols.
Binary Columns were not displayed in the Query Builder of Visual Studio. (Bug #50171)
MySqlCommand.Parameters.Clear() did not work.
UpdateBatchSize property was set to
a value greater than 1, only the first row was applied to the
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
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:
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.
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.