When the length of a VARCHAR column was edited in Table Designer, the data type could be saved incorrectly as BIT. (Bug #13916560)

Any sequence of Take(n) method calls followed by Count or LongCount would cause a System.Data.EntityCommandCompilationException error. (Bug #13913047, Bug #64749)

In “LINQ to Entity” queries, including a child entity (1-n) and its entities (n-n) returned the wrong results. For example:

db.Authors.Include("Books.Editions").AsEnumerable().First();

(Bug #13491698, Bug #62801)

In Visual Studio Table Designer, if you tried to save a new table using an existing table name, subsequently you would not be prompted to choose a new name, preventing you from saving the table. (Bug #13785918)

When creating a Visual Studio Web Application Project, using the ADO.NET Entity Data Model and generating the model from a database, the Entity Framework Model was not created. This operation gave an error:

Access denied for user 'root'@'localhost' (using password: NO)

(Bug #13610452)

When creating a project in VisualStudio using a .NET framework such as 3.0 or 3.5 (anything less than 4.0), the Connector/Net library (MySql.Data.dll) was not listed in the Add References dialog box. The workaround was to browse to the library and add it manually. (Bug #13491678, Bug #60462)

The performance when setting the CommandText property on the MySqlCommand class was improved by enhancing the efficiency of a string comparison operation. (Bug #13739383, Bug #64012)

Fixed MySqlTime parsing to avoid throwing an exception when handling milliseconds (as result of a timediff operation). (Bug #13708884, Bug #64268)

In Visual Studio Table Designer, when adding a second foreign key, the new name was incorrectly assigned to the first foreign key in the list. (Bug #13613824)

In Visual Studio Table Designer, changes to a field were sometimes not detected until you switched focus away from that field. (Bug #13613755)

When using connection pooling, the connections in the pool were not automatically closed upon application exit. With the setting log-warnings=2, you could encounter Aborted connection errors in the MySQL error log. The workaround was to explicitly call MySql.Data.MySqlClient.MySqlConnection.ClearAllPools(); upon exiting the application. (Bug #13629471, Bug #63942)

If MySqlCommand.CommandText was equal to null, then MySqlCommand.ExecuteReader() would throw the wrong exception: NullReferenceException instead of InvalidOperationException. (Bug #13624659, Bug #64092)

In Visual Studio Table Designer, when editing a foreign key relationship, choosing a column name on the left side made that column name unavailable on the right side. (Bug #13615258)

In Visual Studio Table Designer, modifying the Columns field in the Indexes/Keys dialog multiple times could cause an error. (Bug #13613765)

In Visual Studio Table Designer, it was possible to save a new foreign key relationship without filling in the fields of the Foreign Key Relationship dialog. (Bug #13613839)

In Visual Studio Table Designer, changing the length of a VARCHAR field could cause an error. (Bug #13611677)

In Visual Studio Table Designer, an error could occur if you added and deleted column information for foreign keys in a particular sequence. (Bug #13610235)

In Visual Studio Table Designer, deleting a foreign key relationship in the Relationship dialog required clicking twice. (Bug #13610283)

The MySQL script generated by using the function CreateDatabaseScript used names with incorrect singular/plural forms. (Bug #13582837, Bug #62150)

In Visual Studio Table Designer, the Add -> Function Import... dialog could close prematurely when you pressed the Get Column Information button. (Bug #13511736)

When designating a primary key for a table in Table Designer, the key icon could fail to appear until the Table Designer was restarted. (Bug #13481246)

IntelliSense would emit an error when the "-" (minus) character was typed. (Bug #13522344)

After an UPDATE statement, Connector/Net would generate incorrect SELECT SQL statements if a value in the WHERE clause was not also present in the SET clause of the UPDATE. (Bug #13491689, Bug #62134)

In Table Designer for Visual Studio, trying to delete foreign keys from an InnoDB table showed an error, and the change was not saved. (Bug #13481362)

Added better IntelliSense support, including auto-completion when editing stored procedures or .mysql files. For more information, see Section 21.2.3.2, “Using IntelliSense in the SQL Editor”.

Adds a MySqlClientPermission class to help users define the security policies for the database connections within any application using a MySQL database.

Added better partial-trust support, thus allowing Connector/NET to run in a partial trust scenario. It will work correctly in a medium-trust level environment when the library is installed in the GAC. For more information, see Section 21.2.5.18, “Working with Partial Trust”.

Added fractional seconds support, as per MySQL Server 5.6 and above. For more information, see Section 11.3.5, “Fractional Seconds in Time Values”

Added “interceptor” classes for exceptions and commands. For more information, see Section 21.2.5.10, “Using the Connector/Net Interceptor Classes”.

The MySqlDataReader.GetDateTime() method was not recognizing that TIMESTAMP values had already been converted to the local time zone of the MySQL server, which could cause incorrect results if the value was later processed through the ToLocalTime() method. The fix causes the Kind property to be correctly set to Local rather than Unspecified. (Bug #13591554, Bug #63812)

Visual Studio 2010 Table Designer could give an error “Object reference not set to an instance of an object” for schemas with certain combinations of column names and foreign key references. The SQL syntax was incorrect for the ALTER TABLE statement generated by the Table Designer. (Bug #13591545, Bug #63714)