Functionality added or changed:
SSL support has been updated.
The ViewColumns
GetSchema
collection has been updated.
The CommandBuilder.DeriveParameters
function has been updated to the procedure cache.
Improved speed and performance by re-architecting certain sectionsof the code.
Usage Advisor has been implemented. The Usage Advisor checks your queries and will report if you are usiing the connection inefficiently.
The MySqlCommand
object now supports
asynchronous query methods. This is implemented useg the
BeginExecuteNonQuery
and
EndExecuteNonQuery
methods.
Metadata from storaed procedures and stored function execution are cached.
PerfMon hooks have been added to monitor the stored procedure cache hits and misses.
The ShapZipLib library has been replaced with the deflate support provided within .NET 2.0.
Support for the embedded server and client library have been removed from this release. Support will be added back to a later release.
Bugs fixed:
An exception would be raised, or the process would hang, if
SELECT
privileges on a database were not
granted and a stored procedure was used. (Bug#25033)
Nested transactions (which are unsupported)do not raise an error or warning. (Bug#22400)
When adding parameter objects to a command object, if the
parameter direction is set to ReturnValue
before the parameter is added to the command object then when
the command is executed it throws an error. (Bug#25013)
Additional text added to error message (Bug#25178)
Stored procedure executions are not thread safe. (Bug#23905)
Using Driver.IsTooOld()
would return the
wrong value. (Bug#24661)
Deleting a connection to a disconnected server when using the Visual Studio Plugin would cause an assertion failure. (Bug#23687)
When using a DbNull.Value
as the value for
a parameter value, and then later setting a specific value
type, the command would fail with an exception because the
wrong type was implied from the
DbNull.Value
. (Bug#24565)
Ésta es una traducción del manual de referencia de MySQL, que puede encontrarse en dev.mysql.com. El manual de referencia original de MySQL está escrito en inglés, y esta traducción no necesariamente está tan actualizada como la versión original. Para cualquier sugerencia sobre la traducción y para señalar errores de cualquier tipo, no dude en dirigirse a mysql-es@vespito.com.