Running the statement
SHOW PROCESSLIST
would return columns as byte arrays instead of native columns. (Bug #28448)Building a connection string within a tight loop would show slow performance. (Bug #28167)
Using logging (with the
logging=true
parameter to the connection string) would not generate a log file. (Bug #27765)The
UNSIGNED
flag for parameters in a stored procedure would be ignored when usingMySqlCommandBuilder
to obtain the parameter information. (Bug #27679)Using
MySQLDataAdapter.FillSchema()
on a stored procedure would raise an exception:Invalid attempt to access a field before calling Read()
. (Bug #27668)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 thePersist Security Info=False
option set, the cloned connection is not usable because the security information has not been cloned. (Bug #27269)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
Connection Protocol
property within aPropertyGrid
control would raise an exception. (Bug #26472)DataSet wizard would show all tables instead of only the tables available within the selected database. (Bug #26348)
The
characterset
property would not be identified during a connection (also affected Visual Studio Plugin). (Bug #26147, Bug #27240)The
CreateFormat
column of theDataTypes
collection did not contain a format specification for creating a new column type. (Bug #25947)DATETIME
fields from versions of MySQL before 4.1 would be incorrectly parsed, resulting in a exception. (Bug #23342)