MySQL Connector/NET Release Notes
The DbCommandBuilder.QuoteIdentifer
method was not implemented.
(Bug #35492)
Setting the size of a string parameter after the value could cause an exception. (Bug #32094)
Creation of parameter objects with noninput direction using a constructor failed. This was cause by some old legacy code preventing their use. (Bug #32093)
A date string could be returned incorrectly by
MySqlDateTime.ToString()
when the date
returned by MySQL was 0000-00-00 00:00:00
.
(Bug #32010)
A syntax error in a set of batch statements could leave the data adapter in a state that appears hung. (Bug #31930)
Installing over a failed uninstall of a previous version could
result in multiple clients being registered in the
machine.config
. This would prevent certain
aspects of the MySQL connection within Visual Studio to work
properly.
(Bug #31731)
Data cached from the connection string could return invalid information because the internal routines were not using case-sensitive semantics. This lead to updated connection string options not being recognized if they were of a different case than the existing cached values. (Bug #31433)
Column name metadata was not using the character set as defined within the connection string being used. (Bug #31185)
Memory usage could increase and decrease significantly when updating or inserting a large number of rows. (Bug #31090)
Commands executed from within the state change handler would
fail with a NULL
exception.
(Bug #30964)
When running a stored procedure multiple times on the same connection, the memory usage could increase indefinitely. (Bug #30116)
The server error code was not updated in the
Data[]
hash, which prevented
DbProviderFactory
users from accessing the
server error code.
(Bug #27436)
Changing the connection string of a connection to one that changes the parameter marker after the connection had been assigned to a command but before the connection is opened could cause parameters to not be found. (Bug #13991)