Important change: Due to a number of issues with the use of server-side prepared statements, MySQL Connector/Net 5.0.2 has disabled their use by default. The disabling of server-side prepared statements does not affect the operation of the connector in any way.
To enable server-side prepared statements you must add the following configuration property to your connector string properties:
The default value of this property is true.
Implemented a stored procedure cache. By default, the connector caches the metadata for the last 25 procedures that are seen. You can change the number of procedures that are cached by using the
procedure cacheconnection string.
Ignore Prepareoption has been added to the connection string options. If enabled, prepared statements will be disabled application-wide. The default for this option is true.
One system where IPv6 was enabled, MySQL Connector/Net would incorrectly resolve host names. (Bug #23758)
Column names with accented characters were not parsed properly causing malformed column names in result sets. (Bug #23657)
An exception would be thrown when calling
fieldswas null. (Bug #23538)
System.FormatExceptionexception would be raised when invoking a stored procedure with an
ENUMinput parameter. (Bug #23268)
During installation, an antivirus error message would be raised (indicating a malicious script problem). (Bug #23245)
Creating a connection through the Server Explorer when using the Visual Studio Plugin failed. The installer for the Visual Studio Plugin has been updated to ensure that MySQL Connector/Net 5.0.2 must be installed. (Bug #23071)
Using Windows Vista (RC2) as a nonprivileged user would raise a
Registry key 'Global' access denied. (Bug #22882)
Within Mono, using the
PreparedStatementinterface could result in an error due to a
BitArraycopying error. (Bug #18186)
MySQL Connector/Net did not work as a data source for the
SqlDataSourceobject used by ASP.NET 2.0. (Bug #16126)