MySQL Connector/Net 1.0.9 has been released. MySQL Connector/Net is an all-managed ADO.Net provider for MySQL. This release is suitable for use in production environments and with any version of MySQL.
It is now available in source and binary form from the Connector/Net download pages at http://dev.mysql.com/downloads/connector/net/1.0.html and mirror sites (note that not all mirror sites may be up to date at this point of time - if you can't find this version on some mirror, please try again later or choose another download site.)
This release includes many bug fixes along with the following enhancements/changes:
* 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 cache=<size>' connection string setting. You can disable the procedure cache by setting a zero size.
* Shared memory connections now work as expected.
* Queries containing a large number of parameters now run many times faster than before. As an example of the performance gains seen, an internal testing app that needed more than 30 minutes to execute using 1.0.7, completes in less than 8 seconds using 1.0.9.
* We are no longer providing binaries compiled with .NET 1.0 or 2.0 with this branch of the connector. We are doing this for a couple of reasons. First, we believe the vast majority of our users are using .NET 1.1 or 2.0 so not shipping 1.0 binaries reduces our testing workload while affecting a small number of developers. Also, any user building applications with .NET Framework 2.0 should use our new 5.0 product which fully implements the ADO.Net interfaces.
* ICSharpCode ZipLib is no longer used by the connector and is no longer being distributed with it.
* The installer will continue registering the assembly into the Global Assembly Cache. Any user that does not want this behavior is encouraged to download our no-installer packages.
* Turned MySqlPoolManager into a static class and added a static constructor to avoid any race conditions related to initializing the hash table.
* Added 'Ignore Prepare' connection string option for disabling prepared statements application-wide. This was added because we found that server-side prepared statements did not always work as expected. Using this option, a user can continue to use existing code that calls Prepare() while having that call emulated in a non-prepared way. The default for this option is true.
* A nicer exception is displayed if you have added a parameter without the parameter marker.
* Improved CommandBuilder.DeriveParameters to first try and use the procedure cache before querying for the stored procedure metadata.
* Return parameters created with DeriveParameters now have the name RETURN_VALUE.
* Fixed problem with parameter name hashing where the hashes were not getting updated when parameters were removed from the collection. This could cause "item has already been added to the hash" errors.
* Fixed problem where pooled connections that are added back to the idle pool may be still in the closed state.
* Fixed problem where SingleRow and SchemaOnly behaviors now work correctly when calling stored procedures or using server-side prepared statements.
Thank you for checking out this release of Connector/Net.
;lkjasdf;lkjasdf;lkajsdf
ReplyDeleteasdf
ReplyDeleteold version.. but give me lot of money :D
ReplyDeleteMySQL Connector/Net 1.0.9 is now available MySQL list covers managing extracting variables and strings, managing libraries, compiling, formatting.
ReplyDeleteMySQL Connector/Net 1.0 is a fully-managed ADO.NET driver for MySQL. These packages are usable from a .NET 2.0 application but does not support the new features available with ADO.Net 2.0. For those features, you should be using Connector/Net 5.0 or later.
ReplyDeleteI am glad to know that the new version is available. I will check it out.
ReplyDeleteGreat article..
ReplyDeletethanks for sharing.. it can help me
Thanks for sharing.
ReplyDeleteMySQL Connector/Net 1.0 is a fully-managed ADO.NET driver for MySQL. These packages are usable from a .NET 2.0 application but does not support the new features available with ADO.Net 2.0. For those features, you should be using Connector/Net 5.0 or later.
ReplyDeleteThe Microsoft .NET Framework version 2.0 (x86) redistributable package installs the .NET Framework runtime and associated files required to run applications developed to target the .NET Framework v2.0.
ReplyDeleteThis is a tremendous win for JQuery, which already has the momentum of a runaway freight train in a space that has been profoundly fragmented and confused for many years now. It’s also a huge win for Microsoft. Although they’ve been touting their openness to open source concepts and practice for the last few years, Microsoft has also demonstrated its willingness to frustratingly re-invent the wheel in a proprietary fashion
ReplyDeleteConnector/NET enables developers to easily create .NET applications that require secure, high-performance data connectivity with MySQL. It implements the required ADO.NET interfaces and integrates into ADO.NET aware tools. Developers can build applications using their choice of .NET languages. Connector/NET is a fully managed ADO.NET driver written in 100% pure C#.
ReplyDeleteLearn about new MySQL releases, technical articles, events and more. Subscribe Now » ... MySQL Connector/Net 1.0 is a fully-managed ADO.NET driver for MySQL. ... NET 2.0 application but does not support the new features available with ADO.Net 2.0. ... Windows Source and Binaries (ZIP), 1.0.9, 575.0K, Pick a mirror ...
ReplyDeleteDue to a number of issues with the use of server-side prepared statements, 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.
ReplyDeleteTo enable server-side prepared statements you must add the following configuration property to your connector string properties:
ignore prepare=false
MySQL Connector/J is an implementation of the JDBC API for the MySQL relational database server. It strives to conform as much as possible to the API as specified by JavaSoft. It is known to work with many third-party products, including Borland JBuilder, IBM Visual Age for Java, SQL/J, JBoss, Weblogic, IBM WebSphere, Cocobase, ObjectRelationalBridge, etc.
ReplyDeleteVery interesting post - Might be old new, but it was new to me. Thanks.
ReplyDeleteVery interesting post - Might be old new, but it was new to me. Thanks.
ReplyDelete