Error string was returned after a 28000 second
wait_timeout. This has been
changed to generate a
Changed how the procedure schema collection is retrieved. If
use procedure bodies=true then the
mysql.proc table is selected directly as this
is up to 50 times faster than the current
information_schema implementation. If
use procedure bodies=false, then the
information_schema collection is queried.
String escaping functionality has been moved from the
MySqlString class to the
MySqlHelper class, where it can be
accessed by the
GetOrdinal() method failed to
return the ordinal if the column name string contained an
MySQL Connector/Net uninstaller did not clean up all installed files. (Bug #38534)
There was a short circuit evaluation error in the
MySqlCommand.CheckState() method. When
connection == null was true a
NullReferenceException was thrown and not
The provider did not silently create the user if the user did not exist. (Bug #38243)
Executing a command that resulted in a fatal exception did not close the connection. (Bug #37991)
When a prepared insert query is run that contains an
UNSIGNED TINYINT in the parameter list, the
complete query and data that should be inserted is corrupted and
no error is thrown.
In a .NET application MySQL Connector/Net modifies the connection string so that it contains several occurrences of the same option with different values. This is illustrated by the example that follows.
The original connection string:
host=localhost;database=test;uid=*****;pwd=*****; connect timeout=25; auto enlist=false;pooling=false;
The connection string after closing
host=localhost;database=test;uid=*****;pwd=*****; connect timeout=25;auto enlist=false;pooling=false; Allow User Variables=True;Allow User Variables=False; Allow User Variables=True;Allow User Variables=False;
Unnecessary network traffic was generated for the normal case where the web provider schema was up to date. (Bug #37469)
enhancements break existing functionality.
autogenerateschema option produced tables
with incorrect collations.
GetSchema did not work correctly when
querying for a collection, if using a non-English locale.
When reading back a stored double or single value using the .NET provider, the value had less precision than the one stored. (Bug #33322)
Using the MySQL Visual Studio plugin and a MySQL 4.1 server,
certain field types (
not be identified correctly. Also, when looking for tables, the
plugin would list all tables matching a wildcard pattern of the
database name supplied in the connection string, instead of only
tables within the specified database.