MySQL Connector/NET 6.7.6 has been released

[Karen Langford]

Dear MySQL users,

MySQL Connector/NET 6.7.6, 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.5-5.7.

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

Memcached
-------------------------------------------
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.6 (2014-11-11)

   Bugs Fixed

     * Generated code that matched against the start of a
       VARCHAR/CHAR column now correctly uses "LIKE" instead of
       location functions for the LINQ to Entity operators
       "StartsWith", "Contains", and "EndsWith". Locate
       functions do not make use of indexes placed on the
       VARCHAR/CHAR columns, which caused significant
       performance degradation. (Bug #19783747, Bug #19680236,
       Bug #72058)

     * Creating a Geometry Column with an SRID value would not
       save the value to the table. (Bug #19783444, Bug
       #19137999, Bug #19476721, Bug #71869)

     * Generated SQL was missing several clauses, such as
       OrderBy, GroupBy, and Skip), in cases that involved the
       "let" keyword, or in other scenarios that were translated
       into a DbApplyExpression. (Bug #19698010, Bug #19783760,
       Bug #73549)

     * LINQ to Entities queries failed for the cases that
       contained a predicate using IList.Contains with an
       argument of "DbCastExpression, DbConstantExpression,
       DbParameterReferenceExpression". (Bug #19690370, Bug
       #19783755, Bug #73643)

     * A SELECT query that had a nullable DATETIME field in a
       child .Any() clause with an .OrderBy() would fail and
       emit a NotImplementedException exception. (Bug #19681723,
       Bug #19795751, Bug #70722)

     * The query optimization routine would return statements
       with invalid table aliases when nested queries were being
       optimized. This would throw an "Unknown column"
       exception. (Bug #19681348, Bug #72004)

     * The "Feature will be installed when required" option was
       removed from the features list in the Connector/Net
       installer due to it not supporting on-demand
       installations because of dependencies with the
       assemblies. (Bug #19670596, Bug #19681113)

     * The fluent API DbModelBuilder.HasColumnType had no effect
       in Entity Framework 6. (Bug #19476922, Bug #19456229, Bug
       #19462808)

     * Creating a "Model First" or "Database First" model using
       MySQL 5.7 would set ProviderManifestToken to 5.6. (Bug
       #19475012)

     * Setting a Primary Key GUID identity in "Code First" in
       Entity Framework 6 did not function with MySQL server
       5.7. Inserting a row with a valid value for the GUID
       generated an error, even when it had a trigger set to the
       correct value.
       As a workaround, it was necessary to redeclare the column
       definition to accept a dummy default, such as "default
       ''". (Bug #19456452, Bug #19462811, Bug #19476995)

     * Non Primary Keys declared as "Identity GUID" did not have
       their GUID's automatically generated. (Bug #19456415, Bug
       #19461919, Bug #19477029)

     * "LINQ to Entities" queries that used Views with the Take
       operator were not correctly generated. This problem
       affected EF "Database First" scenarios. (Bug #19356006,
       Bug #19789288, Bug #72148)

     * Calling >MySqlConnection.GetSchema("PROCEDURES WITH
       PARAMETERS", ...) would generate an error about a
       non-existent index. This affected Intellisense when
       completing stored procedures. (Bug #19289402)

     * When using Entity Framework 4.3 Code first Identifiers
       for Migrations and Entity Framework 6, generated foreign
       key
       (http://dev.mysql.com/doc/refman/5.6/en/glossary.html#glo
       s_foreign_key) identifiers could be longer than 64
       characters, causing MySQLException errors. The fix
       renames any too-long identifiers using the name format
       FK_guid, where guid is a global unique identifier
       generated at runtime. (Bug #19211564, Bug #19483128)
       References: This bug is a regression of Bug #67285.

     * When the connection limit was exceeded,
       MySqlConnection.Open() would leave the TCP connections in
       a CLOSE_WAIT state, but now closes them. (Bug #18665388,
       Bug #72025)

     * When a client refreshed a web page associated with an
       expired session and if the ASP.NET project was using
       <SessionState ... regenerateExpiredSessionId="true" ...>,
       a "duplicate entry" exception was generated from the
       MySqlSessionProvider. (Bug #18657550, Bug #19783515, Bug
       #70409)

The documentation is available at:
http://dev.mysql.com/doc/refman/5.7/en/connector-net.html

Nuget packages are available at:

https://www.nuget.org/packages/MySql.Data/6.7.6
https://www.nuget.org/packages/MySql.Data.Entity/6.7.6
https://www.nuget.org/packages/MySql.Web/6.7.6

Enjoy and thanks for the support!

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