Running the statement
PROCESSLIST would return columns as byte arrays
instead of native columns.
Building a connection string within a tight loop would show slow performance. (Bug #28167)
Using logging (with the
parameter to the connection string) would not generate a log
UNSIGNED flag for parameters in a stored
procedure would be ignored when using
MySqlCommandBuilder to obtain the parameter
MySQLDataAdapter.FillSchema() on a
stored procedure would raise an exception:
attempt to access a field before calling Read().
If you close an open connection with an active transaction, the transaction is not automatically rolled back. (Bug #27289)
When cloning an open
MySqlClient.MySqlConnection with the
Persist Security Info=False option set, the
cloned connection is not usable because the security information
has not been cloned.
Enlisting a null transaction would affect the current connection object, such that further enlistment operations to the transaction are not possible. (Bug #26754)
Attempting to change the
property within a
PropertyGrid control would
raise an exception.
DataSet wizard would show all tables instead of only the tables available within the selected database. (Bug #26348)
characterset property would not be
identified during a connection (also affected Visual Studio
(Bug #26147, Bug #27240)
CreateFormat column of the
DataTypes collection did not contain a format
specification for creating a new column type.
DATETIME fields from versions of
MySQL before 4.1 would be incorrectly parsed, resulting in a