Functionality Added or Changed
Use Procedure Bodies connection string
option to enable calling procedures without using procedure
Fixed problem with calling stored functions when a return parameter was not given.
Fixed problem with parameter name hashing where the hashes were not getting updated when parameters were removed from the collection.
Return parameters created with DeriveParameters now have the
and marked the
Add(name, value) method as
Fixed problem that prevented use of
command behaviors with stored procedures or prepared statements.
Assembly now properly appears in the Visual Studio 2005 Add/Remove Reference dialog.
Reverted behavior that required parameter names to start with
the parameter marker. We apologize for this back and forth but
we mistakenly changed the behavior to not match what
SqlClient supports. We now support using
either syntax for adding parameters however we also respond
SqlClient in that if you ask for
the index of a parameter using a syntax different from when you
added the parameter, the result will be -1.
Applications would crash when calling with
CommandType set to
MySqlConnection throws an exception when
connecting to MySQL v4.1.7.
Incorrect values/formats would be applied when the
OldSyntax connection string option was used.
High CPU utilization would be experienced when there is no idle
connection waiting when using pooled connections through
Opening a connection would be slow due to host name lookup. (Bug #26152)
method does not work.
When closing and then re-opening a connection to a database, the character set specification is lost. (Bug #25614)
Filling a table schema through a stored procedure triggers a runtime error. (Bug #25609)
Returned data types of a
do not contain the right correct CLR data type.
When connecting to a MySQL Server earlier than version 4.1, the connection would hang when reading data. (Bug #25458)
Registry would be incorrectly populated with installation locations. (Bug #25928)
MySqlConnection.GetSchema fails with
NullReferenceException for Foreign Keys.
Times with negative values would be returned incorrectly. (Bug #25912)
MySQL Connector/Net would not compile properly when used with Mono 1.2. (Bug #24263)
MySQL Connector/Net would fail to install under Windows Vista. (Bug #26430)
ExecuteScalar() with more than one
query, where one query fails, will hang the connection.
MySqlConversionException is raised on
a remote object, the client application would receive a
ConnectionPool error would result
When connecting to a server, the return code from the connection could be zero, even though the host name was incorrect. (Bug #24802)
would throw an exception due to an incorrect table name.
SELECT did not work correctly
when using a
WHERE clause containing a UTF-8