.NET

mysql connector/net 6.0.4 has been released

MySQL Connector/Net 6.0.4, a new version of the all-managed .NET driver
for MySQL has been released.  This is the first post-GA release of the new
6.0 connector and includes several bug fixes from the initial GA release. 

This release is approved for use in all scenarios and officially
supports MySQL servers 4.1 and higher.   It is now available in source and binary form from
[http://dev.mysql.com/downloads/connector/net/6.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.)

IMPORTANT
We have had some reports of installer problems with this package. We are working hard to find the problem. For now it appears that making sure your system is fully updated sometimes helps.  We will release a fix as 6.0.5 once we have solved this issue.

Fixes from 6.0.3
- fixed regression with using stored procedures with datasets (bug #44460)
- fixed compilation under Visual Studio 2005 (bug #44822)
- fixed support for bool data type in entity framework support
- fixed regression where a user could no longer call GetBytes on a GUID column (bug #44507)
- made some fixes to the syntax coloring of sql inside Visual Studio
- fixed display name of triggers inside server explorer
- fixed trigger editing
- fixed tokenization of escaped backslashes (bug #44960)
- fixed conversion of binary(16) type to GUID for entity framework models (bug #44986)
- fixed global Add New menu options with the Visual Studio integration
- improved ad-hoc registration utility so that it handles VS 2005 and VS 2008 properly
- fixed sql that is generated for commands in data set (bug #44512)

New features and improvements
- added Sun Connect registration
- unsigned values are now handled.  Please read the release notes!
- migrated from CTC to VSCT for our menus and buttons.  Also the VisualStudio project will also
  now load and build under VS2005 or VS2008 loading the proper targets files as needed

Enjoy!

new wiki for connector/net

We have started a new project wiki for MySQL Connector/Net.  It’s a little light in content right now but should grow rapidly.  It can be found here.  Please let us know what we can do better.

mysql connector/net 6.0.3 GA has been released

MySQL Connector/Net 6.0.3, a new version of the all-managed .NET driver for MySQL has been released.  This is the first GA release of the new 6.0 connector and introduces several new features and enhancements.  This release is approved for use in all scenarios and officially supports MySQL servers 4.1 and higher.   We had three major goals with this release:  speed, entity framework support, and a better Visual Studio experience.  I’m happy to report that we have met all three.

It is now available in source and binary form from [http://dev.mysql.com/downloads/connector/net/6.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.)

Fixes from 6.0.2

  • fixed broken connection prompting
  • fixed installer that was no longer referencing the right folders for Visual Studio assemblies [bug #44141]
  • made integer column types returned with table and column collections use the same data type when referencing MySql 4.1 servers and MySql 5.0+ servers (bug #44123)
  • lots of unreported bug fixes found in our newly rewritten DDEX provider

New features and improvements

  • Massive speedups.  We have increased the speed of the provider.  In many situations it now matches or exceeds the speed of the native C connector.
  • SQL tokenizing has been improved dramatically.  Not only is it substantially faster (approx 40%) it also now uses a completely rewritten tokenizer that supports all types of stored procedure comments.
  • Added UDF schema collection
  • Implement initial Entity Framework support
  • Improved Visual Studio integration

Visual Studio improvements

We have completely rewritten our Visual Studio integration bits and are delivering several exciting features with it.  Here’s a look at some of those features:

1.  Now uses the same toolbars and commands as SQL Server so the integration is much more seamless.
2.  Uses the native code editor which means code splitting and syntax highlighting.
3.  Change script generation
4.  And many more smaller features…..

Enjoy!

mysql connector/net 5.2.6 has been released

MySQL Connector/Net 5.2.6, a new version of the all-managed .NET driver for MySQL has been released.  This release is of GA quality and is suitable for  use in production environments.  We strongly urge you to  review the change log that is shipped with the product for a thorough review of the changes.

We have a ton of fixes in this release so please review the changelog and see if your favorite bug has been fixed.  This version officially supports all versions of MySQL from 4.1 and later.

It is now available in source and binary form from [http://dev.mysql.com/downloads/connector/net/5.2.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.)

Changes since 5.2.5

  • cleaned up how stored procedure execution operated when the user does or does not have execute privs on the routine (bug #40139)
  • fixed problem with datetime formatting that causes an extra space to be included between the date and time when sent to the server (bug #41021)
  • fixed sproc parameter parsing so that a space between the type and size spec would not cause a problem (bug #41034)
  • removed code from profile provider that overrode Name and Description properties in error.  This had the effect of not allowing you to override those values in the web.config (ug #40871)
  • fixed "metadatacollections" collection to include foreign key columns
  • fixed GetAllProfiles (which is used by several methods).  It had a typo in the SQL and was not including several important columns (bug #41654)
  • fixed problem where the core method GetUser was not properly checking the application id when retrieving user id values.  This would mean that in some cases methods like ValidateUser would return success when they shouldn’t.  (bug #42574)  This triggered several other cleanups in all the providers
  • fixed problem with execution of LOAD DATA LOCAL INFILE (which also affected MySqlBulkLoader). When the driver encountered some type of error opening the local file for transport it would still attempt to close the file which would yield a null reference exception (bug #43332)
  • fixed Sql null value exception when an attempt was made to reset the password and require question and answer was false.  (bug #41408)
  • fixed MySqlDataReader.GetGuid to be more robust in how it attempts to read guid values (bug #41452)
  • fixed bug where attempting to clear a pool twice would result in a null reference exception (bug #42801)
  • Fixed problem with index column schema collection
  • Fixed RemoveUsersFromRoles and DeleteRole where they were not calling transactionscope.Complete. This meant that on systems where the provider tables are transaction aware the changes could be rolled back in every case (bug #43553)
  • Fixed typo in the collection returned when you request the MetaDataCollections collection.  The NumberOfRestrictions column was missing the trailing s. (bug #43990)
  • fixed index and index column schema collections that would fail if you specified the any restrictions more specific than table name (bug #43991)
  • removed a couple of unnecessary lines from NativeDriver.Open() (bug #44028)
  • added connection string option ‘use affected rows’.  (bug #44194)
  • changed MySqlPool so that a freshly pulled connection will issue it’s ping and reset outside of the idlepool lock.  This lessens some of the contention on the idle pool.

Enjoy!

mysql connector/net 6.0.2 beta has been released

Hi,
MySQL Connector/Net 6.0.2, a new version of the all-managed .NET driver for MySQL has been released.  This is a beta release and is intended to introduce you to the new features and enhancements we are planning.  This release should not be used in a production environment.

This release was quickly pushed out due to a problem that caused 6.0.1 to not register with Visual Studio correctly.  We also made a small correction to a previous bug fix.  SQL generated from entity framework for stored procedures will now not directly reference the schema.  This allows the model to move to a different database without need of change.  We had previously made this change for tables but failed to do so for procedures.

It is now available in source and binary form from [http://dev.mysql.com/downloads/connector/net/6.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.)

Please take this version for a test drive and let us know what works and what doesn’t.

mysql connector/net 6.0.1 beta has been released

MySQL Connector/Net 6.0.1, a new version of the all-managed .NET driver for MySQL has been released. This is a beta release and is intended to introduce you to the new features and enhancements we are planning. This release should not be used in a production environment.

We had three major goals with this release. Speed, Entity Framework support, and a better Visual Studio experience. I’m happy to report that we have met all three. Please see the complete list of changes below.

It is now available in source and binary form from [http://dev.mysql.com/downloads/connector/net/6.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.)

  • Massive speedups. We have increased the speed of the provider. In many situations it now matches or exceeds the speed of the native C connector.
  • SQL tokenizing has been improved dramatically. Not only is it substantially faster (approx 40%) it also now uses a completely rewritten tokenizer that supports all types of stored procedure comments.
  • Added UDF schema collection
  • Implement initial Entity Framework support (see below)
  • Improved Visual Studio integration (see below)

Entity Framework support
Yes, we are late to the party but we are here. I apologize for the delays related to this release and I hope that those of you looking to use MySQL with the entity framework will still want to give us a look. This releases uses a entity framework engine that was completely developed in-house and is, therefore, licensed in exactly the same way as our core provider. Please remember that this is an alpha release and we are certain that you will find databases that will not reverse-engineer correctly or you will build models or queries that will not generate correctly. Please file those as bug reports and include all the information you can. We’ll quickly get to those as we are going to move as quickly as possible to GA.

Visual Studio improvements
We have completely rewritten our Visual Studio integration bits and are delivering several exciting features with it. Here’s a look at some of those features:

1. Now uses the same toolbars and commands as SQL Server so the integration is much more seamless.
2. Uses the native code editor which means code splitting and syntax highlighting.
3. Change script generation
4. And many more smaller features…..

Please take this version for a test drive and let us know what works and what doesn’t.

MySql connector/net 6.0 alpha has been released

MySQL Connector/Net 6.0.0, a new version of the all-managed .NET driver for MySQL has been released.  This is an alpha release and is intended to introduce you to the new features and enhancements we are planning.  This release should not be used in a production environment.

We had three major goals with this release.  Speed, Entity Framework support, and a better Visual Studio experience.  I’m happy to report that we have met all three.  Please see the complete list of changes below.

It is now available in source and binary form from [http://dev.mysql.com/downloads/connector/net/6.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.)

  • Massive speedups.  We have increased the speed of the provider.  In many situations it now matches or exceeds the speed of the native C connector.
  • SQL tokenizing has been improved dramatically.  Not only is it substantially faster (approx 40%) it also now uses a completely rewritten tokenizer that supports all types of stored procedure comments.
  • Added UDF schema collection
  • Implement initial Entity Framework support (see below)
  • Improved Visual Studio integration (see below)

Entity Framework support
Yes, we are late to the party but we are here.  I apologize for the delays related to this release and I hope that those of you looking to use MySQL with the entity framework will still want to give us a look.  This releases uses a entity framework engine that was completely developed in-house and is, therefore, licensed in exactly the same way as our core provider.  Please remember that this is an alpha release and we are certain that you will find databases that will not reverse-engineer correctly or you will build models or queries that will not generate correctly. Please file those as bug reports and include all the information you can.  We’ll quickly get to those as we are going to move as quickly as possible to GA.

Visual Studio improvements
Even though these improvements did not make the cutoff for this alpha, you will see them in the next drop.  We have completely rewritten our Visual Studio integration bits and are delivering several exciting features with it.  Here’s a look at some of those features:
1.  Now uses the same toolbars and commands as SQL Server so the integration is much more seamless.
2.  Uses the native code editor which means code splitting and syntax highlighting.
3.  Change script generation
4.  And many more smaller features…..

Please take this version for a test drive and let us know what works and what doesn’t.

MySQL connector/net 5.2.4 has been released

MySQL Connector/Net 5.2.4, a new version of the all-managed .NET driver for MySQL has been released.  This release is of GA quality and is suitable for  use in production environments.  We strongly urge you to  review the change log that is shipped with the product for a thorough review of the changes.

We have a ton of fixes in this release so please review the changelog and see if your favorite bug has been fixed.  Version 5.2.4 works with all versions of MySQL including MySQL-4.1,  MySQL-5.0, MySQL-5.1, and the MySQL-6.0 beta.

It is now available in source and binary form from [http://dev.mysql.com/downloads/connector/net/5.2.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.)

Changes since 5.2.3

  • fixed web providers autogenerateschema option where it would fail if no schema is   present at all (bug #39072)
  • backported fix for lingering problem related to bug #37239.  If two columns had the same name but different case then an exception would be thrown.
  • fixed stored procedure parameter parsing when used inside server explorer.  (bug #39252)
  • fixed time data type so that negative values are handled properly (bug #39275)
  • added runtime check for the mono platform to our Membership provider.  The mono runtime as of 1.9.1 did not support the methods needed for hashed passwords (bug #38895)
  • fixed problem where negative time values with a zero hour would return as positive values (bug #39294)
  • fixed problem where using a stored procedure with parameters with a table adapter was no longer working after our parameter schema changes (bug #39252)
  • fixed problem with profile provider where INSERT .. ON DUPLICATE UPDATE syntax would not work correctly with some older server versions (bug #39330)
  • Defaulting max allowed packet to 1024 to account for the possible case where the value doesn’t come in as a server variable
  • fixed bug #39728 by making MySqlConnectionStringBuilder.GetConnectionString an internal method.   It should not have been publicly available anyway.  It is used internally by the MySqlConnection.ConnectionString property
  • implemented Disposable pattern on MySqlTransaction class so including one in a using statement and then not calling commit will cause a rollback when the using exits (bug #39817)
  • fixed MySqlScript object so that it handles scripts with user variables
  • fixed bug where specifying ‘functions return string=yes’ would cause strings to be returned using the ‘binary’ charset which would not properly render some characters.  Now the connection character set is used. (bug #40076)
  • fixed problem that caused in use connection strings to be modified when a pooled connection timed out and was cancelled.  (bug #40091)
  • fixed problem where using respect binary flags would not use the connection char set and therefore return strings with a bad encoding.
  • fixed bug where provider was attempting to use the new parameters I_S view on servers that didn’t have it (bug #40382)
  • fixed problem where CharSetMap.GetDefaultCollation and CharSetMap.GetMaxLengths might have a thread sync issue on high load systems.  They were not locking the static collections there were initializing. (bug #40231)
  • added GetSByte to the reader for returning tinyint columns (bug #40571)

Thanks for using MySQL Connector/Net!

Using mysql with entity framework webinar

This past Tuesday I was doing more than just voting.  I was giving a live webinar on using MySQL with the Entity Framework.  We had a terrific time (demo machine crash included!) and had a great turnout.  I have been informed that we set records for most number of registrations and attendees.  I’m truly honored and hope that at least some of you got something out of it.

I’ve had a lot of people ask me for the materials from the session so I’ve made them available from my personal server.  You can get the slides, sample projects, and db script here.  The webinar was also recorded and will appear on this page eventually.

Thanks again to all who attended.  I’m hoping to give an expanded version of this session at our users conference in April.  I hope to see some of you there!

am I the last to figure this out?

In my role with Sun I do quite a bit with the Visual Studio SDK.  I develop our ADO.NET provider and the integration code that allows the provider to work inside of Visual Studio.  We support VS 2005 and 2008 with a single binary and, up until now, I’ve used the VS 2005 SDK.  But I’ve had this nagging feeling that I should be able to use the 2008 SDK and the new VSCT format for producing the CTO files.

After some research I discovered that VS 2008 ships with some binding redirects that allows it to use binaries built with the 2005 SDK.  Of course you can always count on Microsoft to make this as hard as possible.  They could keep in mind that out here in the real world we have to support older VS versions and ship the SDK with all necessary tools and assemblies.  But this is Microsoft we are talking about so the regpkg tool that ships with the SDK and helps with assembly registration is tightly bound to the SDK version. 

But the stupidity doesn’t end there.  With some hacking you can get around the regpkg issue (and you can’t ship that tool anyway) but they don’t provide attributes to handle all the registration tasks that are necessary.  Need to register your assembly as a DDEX data provider?  Out of luck.  Need to specify the technology parameter so your DDEX provider works with the proper wizards?  Out of luck.  So, I don’t really give a flip about regpkg and the attributes.

With all that said, I tested building an integration project with the 2008 SDK after making the following changes.  The resources worked great originating as VSCT files. 

   1: <RegisterOutputPackage>false</RegisterOutputPackage>
   2: <RegisterWithCodebase>true</RegisterWithCodebase>
   3: <!-- Make sure we are 2005 compatible, and don't rely on RegPkg.exe 
   4:      of VS2008 which uses Microsoft.VisualStudio.Shell.9.0 -->
   5: <UseVS2005MPF>true</UseVS2005MPF>
   6: <!-- Don't try to run as a normal user (RANA), 
   7:      create experimental hive in HKEY_LOCAL_MACHINE -->
   8: <RegisterWithRanu>false</RegisterWithRanu>

Go to Top