Related Documentation Download these Release Notes
PDF (US Ltr) - 0.8Mb
PDF (A4) - 0.8Mb

MySQL Connector/NET Release Notes  /  Changes in MySQL Connector/Net 6.7  /  Changes in MySQL Connector/NET 6.7.5 (2014-04-04, General Availability)

Changes in MySQL Connector/NET 6.7.5 (2014-04-04, General Availability)

MySQL Connector/Net 6.7.5 is GA release for the 6.7.x series of the .NET driver for MySQL. It can be used for production environments. It is appropriate for use with MySQL server versions 5.0-5.7.

Bugs Fixed

  • Configuring replication and load balancing by passing in multiple servers as a comma-separated list to the connection string failed to function. Threading synchronization problems when using replication (specifically when getting a new server/connection) would also sometimes occur. (Bug #19484568, Bug #18112966, Bug #69832)

  • In Visual Studio, Connector/NET did not read the millisecond portion of a time value for a field of type TIME(3). (Bug #19211409, Bug #18111085)

  • 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 specified in Character String Literal Character Set and Collation, in the MySQL Server manual. (Bug #19211249, Bug #18169145)

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

  • MaximumPoolSize and MinimumPoolSize were not recognized as valid connection string options. (Bug #18182246, Bug #19484670)

  • 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 #19211182, Bug #19483110, 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 #19483069, Bug #71287)

  • 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 #19211293, Bug #69484)

  • 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 #19211384, Bug #69652)

  • 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)

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

  • 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)

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

  • 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)

  • 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)

  • The Installer did not register MySQL in the machine.config as a DbProviderFactories provider. (Bug #17601689, Bug #68760)

  • 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)