MySQL Connector/NET Release Notes
This release fixes bugs since 6.3.5.
Changed how the procedure schema collection is retrieved. If the
connection string contains “use procedure
bodies=true
” then a
SELECT
is performed on the
mysql.proc
table directly, as this is up to
50 times faster than the current Information Schema
implementation. If the connection string contains
“use procedure bodies=false
”,
then the Information Schema collection is queried.
(Bug #36694)
MembershipProvider
did not generate hashes
correctly if the algorithm was keyed. The Key of the algorithm
should have been set if the HashAlgorithm
was
KeyedHashAlgorithm
.
(Bug #58906)
Code introduced to fix bug #54863 proved problematic on .NET version 3.5 and above. (Bug #58853)
The MySqlTokenizer
contained unnecessary
Substring
and Trim
calls:
string token = sql.Substring(startIndex, stopIndex - startIndex).Trim();
The variable token
was not used anywhere in
the code.
(Bug #58757)
MySqlCommand.ExecuteReader(CommandBehavior)
threw a NullReferenceException
when being
called with CommandBehavior.CloseConnection
,
if the SQL statement contained a syntax error, or contained
invalid data such as an invalid column name.
(Bug #58652)
ReadFieldLength()
returned incorrect value
for BIGINT
autoincrement columns.
(Bug #58373)
When attempting to create an ADO.NET Entity Data Model, MySQL connections were not available. (Bug #58278)
MySQL Connector/NET did not support the utf8mb4
character
set. When attempting to connect to utf8mb4
tables or columns, an exception
KeyNotFoundException
was generated.
(Bug #58244)
Installation of MySQL Connector/NET 6.3.5 failed. The error reported was:
MySQL Connector Net 6.3.5 Setup Wizard ended prematurely because of an error. Your system has not been modified.
(Bug #57654)
When the tracing driver was used and an SQL statement was longer than 300 characters, an ArgumentOutOfRangeExcpetion occurred if the statement also contained a quoted character, and the 300th character was in the middle of a quoted token. (Bug #57641)
Calling the Read()
method on a
DataReader
obtained from
MySqlHelper.ExecuteReader
generated the
following exception:
Unhandled Exception: MySql.Data.MySqlClient.MySqlException: Invalid attempt to R ead when reader is closed. at MySql.Data.MySqlClient.MySqlDataReader.Read() at MySqlTest.MainClass.Main(String[] args)
(Bug #57501)
When using MySQL Connector/NET on Mono 2.8 using .NET 4.0, attempting to connect to a MySQL database generated the following exception:
Unhandled Exception: System.MissingMethodException: Method not found: 'System.Data.Common.DbConnection.EnlistTransaction'. at (wrapper remoting-invoke-with-check) MySql.Data.MySqlClient.MySqlConnection:Open ()
(Bug #56509)
Default values returned for text columns were not quoted. This
meant that the COLUMN_DEFAULT
field of the
GetSchema
columns collection did not return a
valid SQL expression.
(Bug #56509)
MySQL Connector/NET for .NET/Mono attempted to dynamically load the assembly
Mono.Posix.dll
when a Unix socket was used
to connect to the server. This failed and the connector was not
able to use a Unix socket unless the
Mono.Posix.dll
assembly was previously
loaded by the program.
(Bug #56410)
The ADO.NET Entity Data Model could not add stored procedures from MySQL Server 5.0.45 but worked fine using MySQL Server 5.1. (Bug #55349)
In the ADO.NET Entity Data Model Wizard, the time to update a model scaled abnormally as the number of entities increased. (Bug #48791, Bug #12596237)