Second Beta release. Fixes bugs since 6.3.2.
Bugs fixed:
MySqlDataAdapter.Update()
generated concurrency violations for custom stored procedure driven update commands that usedUpdateRowSource.FirstReturnedRecord
. (Bug#54895)Several calls to
datadapter.Update()
with intervening changes toDataTable
resulted inConcurrencyException
exceptions being generated. (Bug#54863)MySQL Connector/NET generated a null reference exception when
TransactionScope
was used by multiple threads. (Bug#54681)The icon for the MySQL Web Configuration Tool was not displayed in Visual Studio for Web Application Projects. (Bug#54571)
The
MySqlHelper
object did not have an overloaded version of theExecuteReader
method that accepted aMySqlConnection
object. (Bug#54570)If
MySqlDataAdapter
was used with anINSERT
command where theVALUES
clause contained an expression with parentheses in it, and set theadapter.UpdateBatchSize
parameter to be greater than one, then the call toadpater.Update
either generated an exception or failed to batch the commands, executing each insert individually. (Bug#54386)The method
MySql.Data.Common.QueryNormalizer.CollapseValueList
generated anArgumentOutOfRangeException
. (Bug#54152, Bug#53865)MySQL Connector/NET did not process
Thread.Abort()
correctly, and failed to cancel queries currently running on the server. (Bug#54012)MySQL Connector/NET 6.3.2 failed to install on Windows Vista. (Bug#53975)
Garbage Collector disposal of a
MySqlConnection
object caused the following exception:System.IO.EndOfStreamException: Attempted to read past the end of the stream. MySql.Data.MySqlClient.MySqlStream.ReadFully(Stream stream, Byte[] buffer, Int32 offset, Int32 count) MySql.Data.MySqlClient.MySqlStream.LoadPacket() Outer Exception Reading from the stream has failed. ...
MySQL Connector/NET did not throw an
EndOfStreamException
exception whennet_write_timeout
was exceeded. (Bug#53439)After a timeout exception, if an attempt was made to reuse a connection returned to the connection pool the following exception was generated:
[MySqlException (0x80004005): There is already an open DataReader associated with this Connection which must be closed first.] MySql.Data.MySqlClient.MySqlCommand.CheckState() +278 MySql.Data.MySqlClient.MySqlCommand.ExecuteReader(CommandBehavior behavior) +43 MySql.Data.MySqlClient.MySqlCommand.ExecuteReader() +6 Controls.SimpleCommand.ExecuteReader(String SQL) in ...:323 Albums.GetImagesByAlbum(SimpleCommand Cmd, Int32 iAlbum, String Order, String Limit) in ...:13 Forecast.Page_Load(Object sender, EventArgs e) in ...:70 System.Web.UI.Control.OnLoad(EventArgs e) +99 System.Web.UI.Control.LoadRecursive() +50 System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +627
Membership schema creation failed if the default schema collation was not Latin1. (Bug#53174)
The MySQL Connector/NET installation failed due to
machine.config
files not being present in configuration folders.MySQL Connector/NET has been changed to skip over configuration folders that do not contain a
machine.config
file. (Bug#52352)CHAR(36)
columns were not recognized as GUIDs when used in views with entity models. (Bug#52085)When an application was subjected to increased concurrent load, MySQL Connector/NET generated the following error when calling stored procedures:
A DataTable named \'Procedure Parameters\' already belongs to this DataSet.
When the connection string option “Connection Reset = True” was used, a connection reset used the previously used encoding for the subsequent authentication operation. This failed, for example, if UCS2 was used to read the last column before the reset. (Bug#47153)
When batching was used in
MySqlDataAdapter
, a connection was not opened automatically inMySqlDataAdapter.Update()
. This resulted in anInvalidOperationException
exception being generated, with the message text “connection must be valid and open”.MySQL Connector/NET has been changed to behave more like SQL Server: if the connection is closed, it is opened for the duration of update operation. (Bug#38411)
Database name was emitted into typed datasets. This prevented users using the configured default database. (Bug#33870)