MySQL Forums
Forum List  »  Announcements

MySQL Connector/NET 6.7.5 has been released
Posted by: Karen Langford
Date: April 04, 2014 09:15AM

MySQL Connector/NET 6.7.5, a new version of the all-managed .NET driver
for MySQL has been released.  This is the GA, is feature complete. It is
recommended for production environments.  It is appropriate for use with
MySQL server versions 5.0-5.7.

It is now available in source and binary form from mirror sites
(note that not all mirror sites may be up to date at this point-if you
can't find this version on some mirror, please try again later or choose
another download site.)

The 6.7 version of MySQL Connector/NET brings the following new
-  WinRT Connector.
-  Load Balancing support.
-  Entity Framework 5.0 support.
-  Memcached support for Innodb Memcached plugin.
-  This version also splits the product in two: from now on, starting
   version 6.7, Connector/NET will include only the former Connector/NET
   ADO.NET driver, Entity Framework and ASP.NET providers (Core
   libraries of MySql.Data, MySql.Data.Entity & MySql.Web). While all
   the former product Visual Studio integration (Design support,
   Intellisense, Debugger) are available as part of MySQL Windows
   Installer under the name "MySQL for Visual Studio".

WinRT Connector
Now you can write MySql data access apps in Windows Runtime (aka Store
Apps) using the familiar API of Connector/NET for .NET.

Load Balancing Support
Now you can setup a Replication or Cluster configuration in the backend,
and Connector/NET will balance the load of queries among all servers
making up the backend topology.

Entity Framework 5.0
Connector/NET is now compatible with EF 5, including special features of
EF 5 like spatial types.

Just setup Innodb memcached plugin and use Connector/NET new APIs to
establish a client to MySQL 5.6 server's memcached daemon.

Changes in MySQL Connector/Net 6.7.5 (2014-04-04)

   Bugs Fixed

     * Entity Framework threw a NullReferenceException on insertion
       of a record into tables that had an auto-increment, unsigned,
       bigint primary key. (Bug #18189217, Bug #71242)

     * "MaximumPoolSize" and "MinimumPoolSize" were not recognized as
       valid connection string options. (Bug #18182246)

     * The MySQL parser did not recognize the full string literal
       syntax of [_charset_name]'string' [COLLATE collation_name] as
       supported by the MySQL Server. This fix makes Connector/Net
       and MySQL for Visual Studio recognize the string literal
       syntax as specified in the Character String Literal Character
       Set and Collation
       section of the MySQL Server manual. (Bug #18169145)

     * In Visual Studio, Connector/Net did not read the millisecond
       portion of a time value for a field of type TIME(3). (Bug

     * When Connector/Net's SQL generator emitted code for the LINQ
       Union() or Concat() operator, parentheses were not applied
       around the individual SELECT statements. That could cause a
       change of meaning for the query when a Take() operator (thus a
       LIMIT clause in the SQL code) was applied to the last SELECT
       statement. With this fix, parentheses were put around
       individual SELECT statements, so that the LIMIT clause will
       not be applied to the entire result of the UNION operation.
       (Bug #18049691, Bug #70828)

     * During migrations with ASP.NET Identity 1.0 in Visual Studio,
       the code generator did not generate the indexes and foreign
       keys in the Up() class. (Bug #18049272, Bug #71287)

     * Connector/Net did not add the AUTO_INCREMENT property to a
       primary key column of type BIGINT when creating a model in
       Entity Framework. (Bug #17924407, Bug #17937401, Bug #70602)

     * Millisecond values written to a TIME(6)-typed field of a
       database were wrongly serialized by Connector/Net. (Bug
       #17924388, Bug #70686)

     * The RenameColumn operation in an Entity Framework migration
       threw an "Unknown column 'no' in the 'field list'" error when
       Update-Database was applied. (Bug #17959787, Bug #71102)

     * A MySQL-session-state-enabled web application threw exceptions
       for referencing the wrong table name my_aspnet_Sessions
       (instead of the correct name my_aspnet_sessions). This was due
       to the incorrect case handling of the SQL queries for
       MySqlSessionStateStore. (Bug #17960855, Bug #69652)

     * The value for the Keepalive option in the connection string
       was interpreted by Connector/Net to be in milliseconds. This
       fix makes it to be interpreted as number of seconds, as
       specified in the documentation. (Bug #17981275, Bug #69484)

     * When using the Code First approach in Entity Framework 5,
       automatic migrations failed with the use of foreign keys. (Bug

     * Connector/Net threw a NullReferenceException when trying to
       save an entity into a table with a tinyint or bigint
       auto-incremented primary key. (Bug #17866076, Bug #70888)

     * Could not open the ASP.NET Web Configuration tool in the
       Solution Explorer when using MySQL for Visual Studio 1.0.2 and
       Connector/Net 6.7.5. (Bug #17898244, Bug #69808)

     * Fractional part of a value read by
       MySqlDataReadeer.GetTimeSpan() from a TIME(3)-typed field was
       dropped. (Bug #17923814, Bug #70377)

     * When using the Code First approach in Entity Framework 5, a
       LINQ query that checked whether a nullable column was null
       resulted in a faulty SQL query being generated. (Bug
       #17285548, Bug #69922)

     * Executing a LINQ query containing an order by clause and a
       call to the Contains method using the Take method resulted in
       a bad SQL query, which made reference to a no-existent alias.
       (Bug #17194945, Bug #69751)

The documentation is available at:

Enjoy and thanks for the support!

On behalf of the MySQL Connector/NET and the MySQL/ORACLE RE Team. 

Options: ReplyQuote

Written By
MySQL Connector/NET 6.7.5 has been released
April 04, 2014 09:15AM

Sorry, you can't reply to this topic. It has been closed.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.