Functionality Added or Changed

Bugs Fixed

X DevAPI: The SessionConfig class, SessionConfigManager class, and IpersistenceHandler interface were added for session-configuration management to represent all the information associated with a session.

EF Core: Added all-platform compliance support for the .NET Framework stack (Console, WPF, WinForms, and ASP.NET) and compatibility with ASP.NET 5 when using the .NET Framework or .NET Core version.

Added the following functionality for saving changes in EF Core:

EF Core: A missing function used when a model is added or changed caused the migration generation to fail. MySQLHistoryRepository now implements get_existssql(). (Bug #24804771)

EF Core: An SQL syntax error was emitted when the Contains operator was used in the Where predicate of a LINQ query. This fix requires the use of EF Core version 1.1 or later. (Bug #24797524)

An Entity Framework DbContext object created with a column of type DateTimeOffset returned an error indicating that DateTimeOffset values were incompatible with DateTime and Timestamp values. (Bug #24732001)

X DevAPI: The GetCollections(), GetTable(), and GetTables() methods threw System.InvalidOperationException: name is not a valid column name in the row. (Bug #24385662)

Added support for snapshot change-tracking by recording the original values of an entity when it is retrieved from the database, and support to access the tracked state of entities through DbContext.Entry and DbContext.ChangeTracker.

Added concurrency tokens and shadow properties to the set of conventions used to build an Entity Framework Core model based on the shape of entity classes.

The .NET Core version of the driver now supports connections to MySQL servers configured to use SSL (TSL for 5.7) through the MySqlConnection class or a DbContext with Entity Framework 6.x or Entity Framework Core.

Entity Framework Core support for eager loading can be used to load related data from MySQL as part of the initial query.

Added X DevAPI support for following connections options:

Functionality Added or Changed

Bugs Fixed

Added X DevAPI support for flexible parameter lists that do not require string parsing.

Added X DevAPI support for URI connection strings in the following formats:

Views are no longer implemented using a separate View class in the X DevAPI. Instead, the IsView property has been added to the Table class and views are implemented as tables.

Added in MySql.Data support for .NET Core 1.0, which runs on Windows, OS X, and Linux.

Added in MySQL.Data.EntityFrameworkCore support for Entity Framework (EF) Core (includes support for .NET Framework 4.5.1).

Passing no document or a DbDoc object that contained an empty array to the Add() method of a collection would throw an exception. Now, passing in either an empty document or array of documents returns a Results object in which RecordsAffected is zero. (Bug #23542066)

Passing a DbDoc object that contained an array to the Add() method of a collection would throw an exception. (Bug #23542031)

Functionality Added or Changed

Bugs Fixed

Fixed binary collations as strings instead of bytes.

Added TLS support for TLSv1.1 and TLSv1.2 when connecting to MySQL Server 5.7.

Added results to the Commit() and Rollback() Session X DevAPI methods, in order to read Warnings. This feature has limitations that will be addressed in a future release.

Replaced the use of "@" for "$" in JSON path expressions for X DevAPI usage. This feature has limitations that will be addressed in a future release.

Added X DevAPI support for TLSv1.0. This feature has limitations that will be addressed in a future release.

Functionality Added or Changed

Bugs Fixed

The getLastInsertId() method was renamed to getAutoIncrementValues()

The getLastDocumentIds() method was added to access the last generated ID even when using add()/insert() chaining.

A Column Interface was added.

Bind support was added to NodeSession.SQL().

Support was added to use a URI connection string.

An error was emitted when calling a stored procedure that returned a table.

The FetchOne() method now returns null when there are no more rows, when before it threw an exception.

After Execute() method is called and yields a successful result, parameters are now available to reuse using the same statement.

For NodeSession, the SetCurrentSchema("[schema]") method was added to change the schema in a session using "USE". The GetCurrentSchema() method was added to retrieve the current schema in a session using "SELECT DATABASE()", or return null if a schema is not active.

Setting a database attribute in a connection string now automatically creates a schema object in the session object.

Creating a session using the anonymous type would throw an exception.

Support for compression was extended to the .NET Core version of the driver.

Added support for Entity Framework (EF) Core 1.1.

Functionality Added or Changed

Bugs Fixed

Added TLS support for TLSv1.1 and TLSv1.2 when connecting to MySQL Server 5.7.

Improvements were made to how the connector handles aborted connections. (Bug #23346197, Bug #80997)

With Entity Framework 6, building a table with a primary key would not enclose the key name in quotes, which caused a syntax error. (Bug #22696180, Bug #22696207, Bug #76292)

The connector was not disposing the transaction returned by DBContext.Database.BeginTransaction() when exiting a using code block. (Bug #22514355, Bug #22514363)

When MySQL Monitor Plugin was installed with MySQL Connector/Net from a Windows Installer (.msi) installation package or MySQL Installer, the installation failed. (Bug #21507993)

The connector did not attempt to enumerate stored procedures via mysql.proc(). Instead it looked up stored procedures in INFORMATION_SCHEMA.ROUTINES. This could have led to performance degradation in certain scenarios. (Bug #20960373, Bug #23528155, Bug #74116)

The GB18030 Chinese character set is now supported, a character set that was added in MySQL 5.7.4. (Bug #21098546, Bug #21803306, Bug #21803300)

The JSON type is now supported, a type that was added in MySQL 5.7.8.

Generated columns (GENERATION_EXPRESSION) are now supported, a feature added in MySQL 5.7.6.

The selection of a master or slave now takes into account both the status and mode, when before it only used the mode. Ignoring the status was problematic as, for example, an unreachable server's status is marked as FAULTY while the mode does not change. (Bug #21203824)

Using MySqlConnection.Open() with Connector/Net 6.9.6 would fail and raise the error "Unable to connect to Fabric server". (Bug #20983968)

Connections to MySQL server 5.7 now default to using SSL.

The commercial MySQL Enterprise Monitor plugin was updated to function with TLSv1.1 and TLSv1.2.

The MySqlSimpleRoleProvider.RoleExists method would return true instead of false. (Bug #20325391, Bug #73880, Bug #75397)

With the Driver.GetTimeZoneOffset method, the TimeZone offset was not calculated correctly, and instead it was always set to 0. In other words, this caused the time zone to always be set to UTC. (Bug #20200662, Bug #74134)

With Entity Framework 6, passing in a string reference to the StartWith clause would return incorrect results. (Bug #20129927, Bug #20334228, Bug #20334274, Bug #74918)

Repeatedly calling the MySql.Web.Security.MySqlSimpleMembershipProvider.ValidateUser method could leave open MySQL connections. (Bug #20109419, Bug #75662)

The GetTimeZoneOffset method would return an incorrect value depending on the server Time and TimeZone, as it did not take into account the day into the context of the time difference. (Bug #20065691, Bug #20362040, Bug #20362036, Bug #74905)

The uninstaller process would fail and not remove the connector. (Bug #19485102, Bug #73677)

A connection string that included Chinese characters for a database or uid property would emit the following exception; "MySqlException: Unknown database '???'". (Bug #18141356, Bug #20508130, Bug #70041)

Loading two nested collections could be reported as an invalid SQL query as MySQL Connector/Net only generated a partial query. (Bug #18049862, Bug #20409538, Bug #20409528, Bug #70941)

Functionality Added or Changed

Bugs Fixed

Connector/Net now sends EXPLAIN report data to MySQL Enterprise Monitor as supported by the MySQL server. Before, EXPLAIN data was only sent for SELECT statements.

A SELECT query that had a nullable DATETIME field in a child ".Any()" clause with an ".OrderBy()" would raise an exception. (Bug #19795761)

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 #19944400, Bug #72058)

The web providers registration required the removal of the ".v20" suffix from the type in the web providers section in machine.config. (Bug #19715398, Bug #74080)

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 #19944549, 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 #19944528, 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 #19934324, 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)

A memory leak was fixed. (Bug #19467233, Bug #19474480, Bug #19474510, Bug #73122)

The CreateUser function did not trim whitespace before storing values into the database, while MembershipUser did return trimmed values. The trimming is now performed before the data is stored. (Bug #19453313, Bug #19459461, Bug #19459436, Bug #73411)

Queries with collations using the _utf16le character set were not read correctly and instead yielded a "not presented key in dictionary" error. (Bug #19446614, Bug #19355906, Bug #19446571, Bug #72737)

MySQL Connector/Net would sometimes attempt to call stored procedures when it should not. (Bug #19446554, Bug #19446523, Bug #19325120, Bug #72736)

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

Functionality Added or Changed

Bugs Fixed

MySQL Fabric is now supported. For additional information, see MySQL Fabric Support.

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

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

Adding a new column to an existing model as identity and PK failed when applying the migration. The generated error was: "Incorrect table definition; there can be only one auto column and it must be defined as a key". (Bug #19268382, Bug #19286383)

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

Added the SiteMap and Personalization configuration web providers to the MySql.Web Nuget package.

Added async/await compatible methods

Functionality Added or Changed

Bugs Fixed

Asynchronous methods are now supported.

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)

Functionality Added or Changed

Bugs Fixed

Added a Simple Membership Web Provider.

Added a SiteMap Web Provider.

Added a MySQL Personalization Provider.

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)

Functionality Added or Changed

Bugs Fixed

Added TLS support for TLSv1.1 and TLSv1.2 when connecting to MySQL Server 5.7.

Improvements were made to how the connector handles aborted connections. (Bug #23346197, Bug #80997)

With Entity Framework 6, building a table with a primary key would not enclose the key name in quotes, which caused a syntax error. (Bug #22696180, Bug #22696207, Bug #76292)

The connector was not disposing the transaction returned by DBContext.Database.BeginTransaction() when exiting a using code block. (Bug #22514355, Bug #22514363)

The connector did not attempt to enumerate stored procedures via mysql.proc(). Instead it looked up stored procedures in INFORMATION_SCHEMA.ROUTINES. This could have led to performance degradation in certain scenarios. (Bug #20960373, Bug #23528155, Bug #74116)

Functionality Added or Changed

Bugs Fixed

The GB18030 Chinese character set is now supported, a character set that was added in MySQL 5.7.4. (Bug #21098546, Bug #21803306, Bug #21803300)

The JSON type is now supported, a type that was added in MySQL 5.7.8.

Generated columns (GENERATION_EXPRESSION) are now supported, a feature added in MySQL 5.7.6.

A connection string that included Chinese characters for a database or uid property would emit the following exception; "MySqlException: Unknown database '???'". To solve this, the handshake process was changed to use bytes instead of encoded strings. (Bug #18141356, Bug #70041)

Connections to MySQL server 5.7 now default to using SSL.

With Entity Framework 6, passing in a string reference to the StartWith clause would return incorrect results. (Bug #20129927, Bug #20334228, Bug #20334274, Bug #74918)

The GetTimeZoneOffset method would return an incorrect value depending on the server Time and TimeZone, as it did not take into account the day into the context of the time difference. (Bug #20065691, Bug #20362040, Bug #20362036, Bug #74905)

A memory leak was fixed. (Bug #19467233, Bug #19474480, Bug #19474510, Bug #73122)

The CreateUser function did not trim whitespace before storing values into the database, while MembershipUser did return trimmed values. The trimming is now performed before the data is stored. (Bug #19453313, Bug #19459461, Bug #19459436, Bug #73411)

Queries with collations using the _utf16le character set were not read correctly and instead yielded a "not presented key in dictionary" error. (Bug #19446614, Bug #19355906, Bug #19446571, Bug #72737)

MySQL Connector/Net would sometimes attempt to call stored procedures when it should not. (Bug #19446554, Bug #19446523, Bug #19325120, Bug #72736)

A connection string that included Chinese characters for a database or uid property would emit the following exception; "MySqlException: Unknown database '???'". (Bug #18141356, Bug #20508130, Bug #70041)

Loading two nested collections could be reported as an invalid SQL query as MySQL Connector/Net only generated a partial query. (Bug #18049862, Bug #20409538, Bug #20409528, Bug #70941)

While MySqlDateTime.Millisecond already allowed a value between 0 and 999 (3 digit precision), a new MySqlDateTime.Microsecond property was added to handle microseconds (6 digit precision) on DateTime values. (Bug #20019257)

The "default table cache age" connection string property default is now 60 instead of 0. (Bug #19952133)

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 #19944400, 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 #19944549, 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 #19944528, 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 #19934324, 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)

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)

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

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

Adding a new column to an existing model as identity and PK failed when applying the migration. The generated error was: "Incorrect table definition; there can be only one auto column and it must be defined as a key". (Bug #19268382, Bug #19286383)

When using Entity Framework 4.3 Code first Identifiers for Migrations and Entity Framework 6, generated 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 issue is a regression of: Bug #67285.

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)

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)

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)

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)

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)

The Connector/Net installer failed if .NET Framework 4.0 was not installed.

An error occurred when MySqlProviderFactoryResolver was used with .NET Framework 4.0 and Entity Framework 6.

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)

Code First automatic migration failed with foreign keys when using Entity Framework 5. (Bug #17924399, Bug #70795)

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

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

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)

Model First was broken for string columns with unbounded length.

Stack overflow exceptions were thrown on spatial types.

Functionality Added or Changed

Bugs Fixed

Added idempotent script for Entity Framework 6 migrations.

Removed installer validation when MySQL for Visual Studio is installed.

Changed EF migration history table to use a single column as primary key.

Added support for Entity Framework 6.0

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 wrote wrong version for binding redirects.

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

The GB18030 Chinese character set is now supported, a character set that was added in MySQL 5.7.4. (Bug #21098546, Bug #21803306, Bug #21803300)

The JSON type is now supported, a type that was added in MySQL 5.7.8.

Generated columns (GENERATION_EXPRESSION) are now supported, a feature added in MySQL 5.7.6.

Connections to MySQL server 5.7 now default to using SSL.

With Entity Framework 6, passing in a string reference to the StartWith clause would return incorrect results. (Bug #20129927, Bug #20334228, Bug #20334274, Bug #74918)

The GetTimeZoneOffset method would return an incorrect value depending on the server Time and TimeZone, as it did not take into account the day into the context of the time difference. (Bug #20065691, Bug #20362040, Bug #20362036, Bug #74905)

A memory leak was fixed. (Bug #19467233, Bug #19474480, Bug #19474510, Bug #73122)

The CreateUser function did not trim whitespace before storing values into the database, while MembershipUser did return trimmed values. The trimming is now performed before the data is stored. (Bug #19453313, Bug #19459461, Bug #19459436, Bug #73411)

Queries with collations using the _utf16le character set were not read correctly and instead yielded a "not presented key in dictionary" error. (Bug #19446614, Bug #19355906, Bug #19446571, Bug #72737)

MySQL Connector/Net would sometimes attempt to call stored procedures when it should not. (Bug #19446554, Bug #19446523, Bug #19325120, Bug #72736)

A connection string that included Chinese characters for a database or uid property would emit the following exception; "MySqlException: Unknown database '???'". (Bug #18141356, Bug #20508130, Bug #70041)

Loading two nested collections could be reported as an invalid SQL query as MySQL Connector/Net only generated a partial query. (Bug #18049862, Bug #20409538, Bug #20409528, Bug #70941)

While MySqlDateTime.Millisecond already allowed a value between 0 and 999 (3 digit precision), a new MySqlDateTime.Microsecond property was added to handle microseconds (6 digit precision) on DateTime values. (Bug #20019257)

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 #19944400, 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 #19944549, 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 #19944528, 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 #19934324, 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)

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)

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

"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 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 issue 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)

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)

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

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)

When using Entity Framework 5.0, some string patterns in a LINQ query caused MySQL to throw syntax errors when they were passed to the Contains(), StartsWith(), or EndsWith() methods. (Bug #16974405, Bug #69409)

The installation of "MySQL for Visual Studio 1.0.2" was broken after installing Connector/NET 6.7.x, because the data provider was not found after uninstalling MySQL for Visual Studio. (Bug #16973456)

The LINQ query would return the error "An error of "Unknown column 'Distinct1.nCdSite' in 'where clause'" when using Distinct().Count(). (Bug #16950146, Bug #68513)

When using automatic migrations in Entity Framework 5.0, the database objects were given the 'dbo' prefix. This incorrect prefix is no longer generated. (Bug #16909439)

When the IIS application pool reset the worker processes at a specific time, the MySQL session state store would crash the w3wp.exe process and the request resulted in a crash error message. There are no longer ASP.NET crash yellow pages or bad exceptions. Session expiration is now handled properly. (Bug #16909237, Bug #67665)

Connector/NET threw a fatal error when trying to read a MySQL table that used the UTF-16 or UTF-32 character set. Mappings for UTF-16 and UTF-32 encodings have now been added. (Bug #16776818, Bug #69169)

An "DBUpdateException saving changes" exception was thrown while inserting data that had Identify columns. The data is now stored in the table.

A workaround was to set global sql_mode = "ANSI";. (Bug #16494585)

Sometimes data was not returned when a socket connection was slow, interrupted, or delayed. The timeout is now properly reported as an error to the upper layers. (Bug #69039, Bug #16950212)

Using a nested projection causes a malformed query to be created, and spurious data to be returned. (Bug #67183, Bug #16872852)

Generated "LINQ to Entities" queries are no longer as nested. In other words, two similar queries with one nested inside the other are now flattened into a simple query. This provides better performance for large result sets. (Bug #65723, Bug #16973939)

An exception was thrown when populating DataTable with query fields containing a UNIQUE index or constraint NULL. There is no longer an exception thrown, and the DataTable.Fill method terminates correctly (filling the data). (Bug #65065, Bug #16952323)

Functionality Added or Changed

Bugs Fixed

Added support for Entity Framework 5.0 when using .NET 4.0.

The Load Balancing and Replication functionality was unstable. (Bug #16762427)

Functionality Added or Changed

Bugs Fixed

WinRT support was added.

The Connector/NET installation wizard was installing the same version of MySQL.Data (v2.0.50727) to all of the assemblies. (Bug #16725274)

The core assemblies were not listed in the Add Reference dialog for .NET 4.5. Only 4.0 assemblies were listed. (Bug #16704115, Bug #16463655)

The Migration functionality failed when using Entity Framework 5.0 with Connector/Net 6.7. (Bug #16694050)

Running the "Repair" option with the Connector/Net installation wizard would break the installation. (Bug #16630567)

The "Bug Geometry Provider Incompatible Exception" is now handled. (Bug #16453250)

Functionality Added or Changed

Bugs Fixed

Connector/Net now supports SHA-256 hashing for user account passwords. After you create an account following the steps outlined in The SHA-256 Authentication Plugin, just open a Connector/Net connection passing user and password. This feature works in both SSL and non-SSL secured connections. (Bug #15935128)

Connector/Net now supports the MySQL 5.6 feature to store connection-specific data in the server. A Connector/Net application can supply to the server a list of key/value pairs at login time. When you specify the connection option Connect_Attrs, a predefined set of attribute values is sent to the server. Connector/Net automatically transmits the following attributes:

To examine these connection-specific attributes on the server, query the Performance Schema tables described in Performance Schema Connection Attribute Tables. (Bug #15935112)

Connector/Net now supports the MySQL 5.6 password expiration protocol. See ALTER USER for the syntax to expire the password for a user. When you open a connection through Connection/Net that logs in as a user with an expired password, any statement issued through the connection produces a SET PASSWORD exception. When you create a connection in Visual Studio Server Explorer to a user with an expired password, a dialog prompts for a new password, after which the connection succeeds. (Bug #15935104)

When defining an entity with a DatabaseGeneratedOption.Identity value with Entity Framework Code First, you can now leave this column out of the column list for an INSERT or UPDATE statement. This feature is especially useful for defining a column with a default value corresponding to the CURRENT_TIMESTAMP() return value:

[DatabaseGenerated(DatabaseGeneratedOption.Identity)]
public DateTime DateCreated { get; set; }

(Bug #15935094)

The Geometry type is now supported, with MySQL Server 5.1 and above.

New geometry columns were not compatible with the DbGeometry class. (Bug #16446399)

Setting cascadeDelete to true in DbMigration.AddForeignKey() results in ON DELETE RESTRICT foreign key constraints in generated DDL, rather than ON DELETE CASCADE as expected. (Bug #16398432, Bug #68457)

When running a multi-threaded service, you might receive the exception:

The given key was not present in the dictionary

The issue was fixed by enhancing the locking code within the ConnectionStringBuilder class. (Bug #16310698, Bug #68217)

When using EntityFramework 4.3 and Code First, generated 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 #16286397, Bug #67285)

Connector/Net would throw a MySqlException exception when an invalid collection was passed to the GetSchema method. Now it throws an ArgumentException when an invalid collection name is passed to GetSchema, to be compliant with the API spec of System.Data.Common.DbConnection.GetSchema. The new behavior provides better compatibility with other data access providers such as ADO.Net. (Bug #16271425, Bug #67901)

If a DateTime type in MySQL 5.6 was defined with milliseconds precision using Entity Framework Code First or EF Model First, the expected DateTime(n) column did not include the precision specification. (Bug #15972773)

Calling the method FirstOrDefault “LINQ to Entities” queries caused a System.Data.EntityCommandCompilationException exception. (Bug #15856964, Bug #67377)

When using Entity Frameworks: Code First in Visual Studio 2012 and using a GUID as the primary key in a class, the following error could occur:

Incorrect column specifier for column 'column_name'.

Connector/Net was applying the AUTO_INCREMENT attribute to the column, which requires that the column use an integer data type. (Bug #15834176, Bug #67450)

Connection attempts using IPV6 addresses in Connector/Net would fail. (Bug #14835718, Bug #67253)

Specifying the Default Command Timeout option in a connection string used with the MySQL Entity Framework provider had no effect. The command timeout was always 30 seconds. (Bug #14825670, Bug #67171)

Visual Studio 2012 projects could sometimes give the following error dialog:

Failed to merge object(s).

Keyword not supported.
Parameter name: AttachDbFilename.

This issue affected mostly VisualStudio 2012 projects, either migrated from VisualStudio 2010 or including web sites created with VS2010, connecting to a MySQL 5.5 server. (Bug #14733472, Bug #66880)

A System.InvalidCastException exception could occur when calling a stored function. A workaround was to specify the CheckParameters=false connection option. (Bug #13864627, Bug #64633)

Some keywords would not work as IDs without quoting in the parser.

The error message was improved for when attempting to authenticate with an old password.

While MySqlDateTime.Millisecond already allowed a value between 0 and 999 (3 digit precision), a new MySqlDateTime.Microsecond property was added to handle microseconds (6 digit precision) on DateTime values. (Bug #20019257)

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

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)

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

When using Entity Framework 4.3 Code first Identifiers for Migrations and Entity Framework 6, generated 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 issue is a regression of: Bug #67285.

When trying to alter a stored procedure or trigger that included references to session variables, an error occurred and the changes were not saved, unless "Allow User Variables=true" was set in the connection settings. An error is no longer generated, and similar issues with renaming stored procedures or triggers using Alter Routine were also fixed. (Bug #19211432)

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)

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)

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)

In Visual Studio, the stored procedure debugger did not evaluate the last_insert_id() function in a watch expression correctly. This fix also corrects similar issues for two other information functions that query the debug data table: row_count() and found_row(). (Bug #18111085)

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)

The MySQL parser could not parse an if statement when there were any spaces before the parenthesis for the arguments (for example, “if (1,1, 1)”). Besides if, the same issue occurred for a number of other functions like row_count, ifnull, mod, repeat, and so on, and this fix corrects the problem for all of them. (Bug #17981407, Bug #19211240)

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)

In Visual Studio, Intellisense did not treat the keywords “describe” and “desc” as synonyms of “explain”. (Bug #17956087, Bug #19211401)

In Visual Studio, Intellisense showed views from all databases, instead of just the current one. (Bug #17954412, Bug #19211338)

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)

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

Sometimes invoking the IntelliSense code completion (Control + J) on a MySQL file would emit an error. (Bug #17890216)

When opening or creating a .mysql file, trying to invoke Intellisense caused an error in some cases. (Bug #17890216)

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)

Debugger failed to debug a routine correctly when it had two functions in a single expression. That was due to an error in handling the scope of the second function, which has been fixed. (Bug #17865915)

In Visual Studio, the debugger failed with parser errors when debugging stored procedures with a Leave statement. (Bug #17616344)

When debugging a stored routine in Visual Studio with the debugger, long identifiers caused the error "data too long for column 'pvarname'" to be thrown. That was because the SQL script of the debugger did not support the same lengths for identifier names as the MySQL server does. This fix matches the debugger with the MySQL server on the maximum lengths supported for identifier names. (Bug #17568158, Bug #70159)

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)

When using Entity Framework 5.0, some string patterns in a LINQ query caused MySQL to throw syntax errors when they were passed to the Contains(), StartsWith(), or EndsWith() methods. (Bug #16974405, Bug #69409)

The LINQ query would return the error "An error of "Unknown column 'Distinct1.nCdSite' in 'where clause'" when using Distinct().Count(). (Bug #16950146, Bug #68513)

When the IIS application pool reset the worker processes at a specific time, the MySQL session state store would crash the w3wp.exe process and the request resulted in a crash error message. There are no longer ASP.NET crash yellow pages or bad exceptions. Session expiration is now handled properly. (Bug #16909237, Bug #67665)

When using Entity Framework 4.3.1 and Code First Migrations, databases were migrated more than once. This fix stops the problem by changing the CreatedOn column in the migration history table to use the 24-hour time format. (Bug #16869202, Bug #68889)

Connector/NET threw a fatal error when trying to read a MySQL table that used the UTF-16 or UTF-32 character set. Mappings for UTF-16 and UTF-32 encodings have now been added. (Bug #16776818, Bug #69169)

An "DBUpdateException saving changes" exception was thrown while inserting data that had Identify columns. The data is now stored in the table.

A workaround was to set global sql_mode = "ANSI";. (Bug #16494585)

After opening a stored routine in the SQL Editor in Visual Studio and then changing its name, an error occurred with the message "Unable to load the stored procedure for editing" at the attempt to save the routine. (Bug #16390757)

When running a multi-threaded service, you might receive the exception:

The given key was not present in the dictionary

The issue was fixed by enhancing the locking code within the ConnectionStringBuilder class. (Bug #16310698, Bug #68217)

When using EntityFramework 4.3 and Code First, generated 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 #16286397, Bug #67285)

Connector/Net would throw a MySqlException exception when an invalid collection was passed to the GetSchema method. Now it throws an ArgumentException when an invalid collection name is passed to GetSchema, to be compliant with the API spec of System.Data.Common.DbConnection.GetSchema. The new behavior provides better compatibility with other data access providers such as ADO.Net. (Bug #16271425, Bug #67901)

When using Entity Frameworks: Code First in Visual Studio 2012 and using a GUID as the primary key in a class, the following error could occur:

Incorrect column specifier for column 'column_name'.

Connector/Net was applying the AUTO_INCREMENT attribute to the column, which requires that the column use an integer data type. (Bug #15834176, Bug #67450)

Specifying the Default Command Timeout option in a connection string used with the MySQL Entity Framework provider had no effect. The command timeout was always 30 seconds. (Bug #14825670, Bug #67171)

A System.InvalidCastException exception could occur when calling a stored function. A workaround was to specify the CheckParameters=false connection option. (Bug #13864627, Bug #64633)

Sometimes data was not returned when a socket connection was slow, interrupted, or delayed. The timeout is now properly reported as an error to the upper layers. (Bug #69039, Bug #16950212)

Using a nested projection causes a malformed query to be created, and spurious data to be returned. (Bug #67183, Bug #16872852)

Generated "LINQ to Entities" queries are no longer as nested. In other words, two similar queries with one nested inside the other are now flattened into a simple query. This provides better performance for large result sets. (Bug #65723, Bug #16973939)

An exception was thrown when populating DataTable with query fields containing a UNIQUE index or constraint NULL. There is no longer an exception thrown, and the DataTable.Fill method terminates correctly (filling the data). (Bug #65065, Bug #16952323)

Functionality Added or Changed

Bugs Fixed

Connector/Net now supports SHA-256 hashing for user account passwords. After you create an account following the steps outlined in The SHA-256 Authentication Plugin, just open a Connector/Net connection passing user and password. This feature works in both SSL and non-SSL secured connections. (Bug #15935128)

Connector/Net now supports the MySQL 5.6 feature to store connection-specific data in the server. A Connector/Net application can supply to the server a list of key/value pairs at login time. When you specify the connection option Connect_Attrs, a predefined set of attribute values is sent to the server. Connector/Net automatically transmits the following attributes:

To examine these connection-specific attributes on the server, query the Performance Schema tables described in Performance Schema Connection Attribute Tables. (Bug #15935112)

Connector/Net now supports the MySQL 5.6 password expiration protocol. See ALTER USER for the syntax to expire the password for a user. When you open a connection through Connection/Net that logs in as a user with an expired password, any statement issued through the connection produces a SET PASSWORD exception. When you create a connection in Visual Studio Server Explorer to a user with an expired password, a dialog prompts for a new password, after which the connection succeeds. (Bug #15935104)

When defining an entity with a DatabaseGeneratedOption.Identity value with Entity Framework Code First, you can now leave this column out of the column list for an INSERT or UPDATE statement. This feature is especially useful for defining a column with a default value corresponding to the CURRENT_TIMESTAMP() return value:

[DatabaseGenerated(DatabaseGeneratedOption.Identity)]
public DateTime DateCreated { get; set; }

(Bug #15935094)

If a DateTime type in MySQL 5.6 was defined with milliseconds precision using Entity Framework Code First or EF Model First, the expected DateTime(n) column did not include the precision specification. (Bug #15972773)

Calling the method FirstOrDefault “LINQ to Entities” queries caused a System.Data.EntityCommandCompilationException exception. (Bug #15856964, Bug #67377)

Connection attempts using IPV6 addresses in Connector/Net would fail. (Bug #14835718, Bug #67253)

Visual Studio 2012 projects could sometimes give the following error dialog:

Failed to merge object(s).

Keyword not supported.
Parameter name: AttachDbFilename.

This issue affected mostly VisualStudio 2012 projects, either migrated from VisualStudio 2010 or including web sites created with VS2010, connecting to a MySQL 5.5 server. (Bug #14733472, Bug #66880)

In Visual Studio 2005, adding a new data connection through the Server Explorer produced an error message: Package Load Failure. The Visual Studio plugin was dynamically linked against VS2008 version of assembly Microsoft.VisualStudio.Data (v9.0). The fixed plugin links with the VS2005 version (v8.0) of that library instead, which is upward compatible with later Visual Studio versions. (Bug #13491674, Bug #63073)

Functionality Added or Changed

Bugs Fixed

The medium trust support using the MySQLClientPermissions class is now more flexible: in addition to the original deployment method, where the library is installed in the Global Assembly Cache (GAC), you can also install the library within a bin or lib folder inside the project or solution. When the library is deployed somewhere other than the GAC, the only protocol supported is TCP/IP. Existing applications that use the library installed in the GAC must now include an extra connection option, includesecurityasserts=true. For details, see Working with Partial Trust / Medium Trust. (Bug #14668820, Bug #65036)

Since Connector/Net 6.5, TIMESTAMP values have been returned as DateTime objects with a kind property of Local rather than Unspecified. MySqlDataReader.GetDateTime() should have returned a date with a kind property of UTC when the time_zone connection property was utc. With this fix, if time_zone is UTC, Kind is also UTC; otherwise, Kind is Local.

To work with multiple servers with different timezones, change the time_zone setting to UTC in all MySqlConnection objects. For example, if you issue the command:

set @@global.time_zone = '+0:00',

then every new connection you open, or the current connection if you close and reopen it, will use the new client time zone. With this fix, you will not have to change system_time_zone of any of your servers. Connector/NET checks if client time zone differs from UTC by running a query like:

select timediff( curtime(), utc_time() )

where a return value of zero hours means UTC is being used for time_zone.

With Kind = UTC, you can use .NET standard APIs to translate between time zones for frontend applications when required. (Bug #14740705, Bug #66964)

When an application starts up, creates a connection, and then goes idle after a single database operation, the connections are now cleaned up more quickly: typically after an idle time of 3 minutes rather than 6 minutes. This optimization is especially useful for ASP.net applications on low-traffic sites. (Bug #14652624, Bug #66472)

Functionality Added or Changed

Bugs Fixed

You can now write a custom authentication plugin, taking advantage of the pluggable authentication feature available in MySQL 5.5.16 and higher. See Writing a Custom Authentication Plugin for details.

Under some circumstances, setting CacheServerProperties=true in the connection string could cause a Packet too large error. With connection pooling enabled and CacheServerProperties=true, the first connection worked as expected, but the second, third, and so on connections failed if the query exceeded 1024 bytes. (Bug #14593547, Bug #66578)

Connector/Net did not support creating an entity with a key of type string. During database creation, a MySqlException was thrown saying BLOB/TEXT column 'Name' used in key specification without a key length. The DDL produced by the provider specified a MEDIUMTEXT column for the primary key without specifying a length for the key. This fix is particularly important when working with Entity Framework versions 4.3 and later, since the __MigrationsHitory table (which replaces the EdmMetadata table) uses a string property as its key. (Bug #14540202, Bug #65289, Bug #64288)

The ExecuteNonQuery() could return an error Parameter '?' must be defined, when attempting to execute a statement such as:

insert into table_name (Field1, Field1) VALUES(?,?)

That is, when referencing the same field twice with two different ? placeholders. (Bug #14499549, Bug #66060)

When using a MySQL database set up as UTF32 as an ASP.net membership database, web applications could give a “key too long” error, and the Website Administration Tool would not connect to providers. The cause was that the column my_aspnet_sessions.SessionId, when converted from Latin1 character set to UTF32 with 4 bytes per character, exceeded the length limit for a primary key:

Specified key was too long; max key length is 767 bytes

(Bug #14495292, Bug #65144)

The MySQL Connector/Net EntityFramework provider would throw NullReferenceException when trying to insert a new record with an empty VALUES clause. Such an INSERT should work when the only required (NOT NULL) column in the table is a primary key auto-increment column. (Bug #14479715, Bug #66066)

Using the Entity Data Model Designer decimal type and CreateDatabase function, the values were stored with 0 digits at the right of the decimal point. With this fix, the default is 2 digits to the right of the decimal point, and any precision specified through the Entity Data Model Designer is applied correctly. (Bug #14474342, Bug #65127)

Customizing precision by calling the HasPrecision() method within the OnModelCreating() method in a Code First project would always produce precision settings (10,2) rather than the specified precision. (Bug #14469048, Bug #65001)

When building commands through the MySql.Data.MySqlClient.MySqlCommand() class, memory could be leaked because some IO.MemoryStream instances were not being freed efficiently. The memory leak could be an issue in SQL-heavy applications, for example a logging application processing large numbers of INSERT statements. (Bug #14468204, Bug #65696)

When using the ASP.net web security functionality with a MySQL database, using features that access the my_aspnet_usersinroles table caused an exception:

MySql.Data.MySqlClient.MySqlException: Table 'testdb.my_aspnet_usersinrole' doesn't exist.

For example, this error could occur when trying to remove the user from a role or find users in a role. The fix corrects the spelling of the table name to my_aspnet_usersinroles. (Bug #14405338, Bug #65805)

Although the member variable MySqlCommand.LastInsertedId was a 64-bit long, its value was effectively capped at the maximum value of Int32 (2,147,483,647). If a primary key exceeded this value, the value of LastInsertedId was wrong. This mismatch could be an issue for tables with large numbers of rows. (Bug #14171960, Bug #65452)

When using the Entity Framework Code First approach, the generated code could be use the MEDIUMTEXT data type in contexts where other types such as VARCHAR were more appropriate, leading to errors such as:

error 0064: Facet 'MaxLength' must not be specified for type 'mediumtext'.

(Bug #13582335, Bug #63920)

This beta release removes several of the earlier limitations on stored procedure debugging:

These limitations remain:

Stored procedure debugging in Microsoft Visual Studio.

Entity Framework 4.3 Code First support.

Pluggable authentication (not available in this alpha).

Entity Framework Code First Support

Stored Procedure Debugging

Bugs Fixed

To support the Entity Framework 4.3.1, Connector/Net can now use the Code First approach when developing against a model, and keep track of the changes in the Entity Model and in the Database. This new Entity Framework 4.3.1 feature is focused in allowing your database to be updated along with your Code First Model changes.

The Connector/Net integration with Visual Studio now includes stored procedure debugging. It works in a very intuitive manner, by simply clicking Debug Routine from Server Explorer. The limitations in this preliminary alpha release include:

When using Entity Framework with Connector/Net, the association property OnDelete was not taken into account in the CreateDatabaseScript function of the ObjectContext, leading to an error message System.Data.UpdateException was unhandled. The SQL generated by the CreateDatabaseScript function was missing ON DELETE and ON UPDATE clauses. These clauses were filled in correctly by the DDL generation wizard. (Bug #14008752, Bug #64779)

A call to a stored procedure or function in an application using the Code First entity framework could result in an error:

Unhandled Exception: MySql.Data.MySqlClient.MySqlException: You have an error
in your SQL syntax; ...

The code change allows syntax such as the following to invoke a stored procedure, without using the CALL statement and without using CommandType.StoredProcedure.

int count = myContext.Database.SqlQuery<int>("GetCount").First();

(Bug #14008699, Bug #64999)

When using the Entity Framework Code First approach, the generated code could be incorrect:

(Bug #13900091, Bug #64216)

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)

When using Entity Framework 5.0, some string patterns in a LINQ query caused MySQL to throw syntax errors when they were passed to the Contains(), StartsWith(), or EndsWith() methods. (Bug #16974405, Bug #69409)

The LINQ query would return the error "An error of "Unknown column 'Distinct1.nCdSite' in 'where clause'" when using Distinct().Count(). (Bug #16950146, Bug #68513)

When the IIS application pool reset the worker processes at a specific time, the MySQL session state store would crash the w3wp.exe process and the request resulted in a crash error message. There are no longer ASP.NET crash yellow pages or bad exceptions. Session expiration is now handled properly. (Bug #16909237, Bug #67665)

Connector/NET threw a fatal error when trying to read a MySQL table that used the UTF-16 or UTF-32 character set. Mappings for UTF-16 and UTF-32 encodings have now been added. (Bug #16776818, Bug #69169)

An "DBUpdateException saving changes" exception was thrown while inserting data that had Identify columns. The data is now stored in the table.

A workaround was to set global sql_mode = "ANSI";. (Bug #16494585)

Sometimes data was not returned when a socket connection was slow, interrupted, or delayed. The timeout is now properly reported as an error to the upper layers. (Bug #69039, Bug #16950212)

Using a nested projection causes a malformed query to be created, and spurious data to be returned. (Bug #67183, Bug #16872852)

Generated "LINQ to Entities" queries are no longer as nested. In other words, two similar queries with one nested inside the other are now flattened into a simple query. This provides better performance for large result sets. (Bug #65723, Bug #16973939)

An exception was thrown when populating DataTable with query fields containing a UNIQUE index or constraint NULL. There is no longer an exception thrown, and the DataTable.Fill method terminates correctly (filling the data). (Bug #65065, Bug #16952323)

Functionality Added or Changed

Bugs Fixed

Connector/Net now supports SHA-256 hashing for user account passwords. After you create an account following the steps outlined in The SHA-256 Authentication Plugin, just open a Connector/Net connection passing user and password. This feature works in both SSL and non-SSL secured connections. (Bug #15935128)

Connector/Net now supports the MySQL 5.6 feature to store connection-specific data in the server. A Connector/Net application can supply to the server a list of key/value pairs at login time. When you specify the connection option Connect_Attrs, a predefined set of attribute values is sent to the server. Connector/Net automatically transmits the following attributes:

To examine these connection-specific attributes on the server, query the Performance Schema tables described in Performance Schema Connection Attribute Tables. (Bug #15935112)

Connector/Net now supports the MySQL 5.6 password expiration protocol. See ALTER USER for the syntax to expire the password for a user. When you open a connection through Connection/Net that logs in as a user with an expired password, any statement issued through the connection produces a SET PASSWORD exception. When you create a connection in Visual Studio Server Explorer to a user with an expired password, a dialog prompts for a new password, after which the connection succeeds. (Bug #15935104)

When defining an entity with a DatabaseGeneratedOption.Identity value with Entity Framework Code First, you can now leave this column out of the column list for an INSERT or UPDATE statement. This feature is especially useful for defining a column with a default value corresponding to the CURRENT_TIMESTAMP() return value:

[DatabaseGenerated(DatabaseGeneratedOption.Identity)]
public DateTime DateCreated { get; set; }

(Bug #15935094)

Setting cascadeDelete to true in DbMigration.AddForeignKey() results in ON DELETE RESTRICT foreign key constraints in generated DDL, rather than ON DELETE CASCADE as expected. (Bug #16398432, Bug #68457)

After opening a stored routine in the SQL Editor in Visual Studio and then changing its name, an error occurred with the message "Unable to load the stored procedure for editing" at the attempt to save the routine. (Bug #16390757)

When running a multi-threaded service, you might receive the exception:

The given key was not present in the dictionary

The issue was fixed by enhancing the locking code within the ConnectionStringBuilder class. (Bug #16310698, Bug #68217)

When using EntityFramework 4.3 and Code First, generated 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 #16286397, Bug #67285)

Connector/Net would throw a MySqlException exception when an invalid collection was passed to the GetSchema method. Now it throws an ArgumentException when an invalid collection name is passed to GetSchema, to be compliant with the API spec of System.Data.Common.DbConnection.GetSchema. The new behavior provides better compatibility with other data access providers such as ADO.Net. (Bug #16271425, Bug #67901)

When debugging a stored routine containing a DECIMAL variable, you might encounter the error:

mismatched input ')' expecting COMMA

A workaround was to include a second parameter of 0 in the variable declaration:

DECLARE var_name DECIMAL(3, 0)

The fix allows the Connector/Net debugger to handle DECIMAL variable declarations without the optional second field. (Bug #16079735, Bug #67975)

If a DateTime type in MySQL 5.6 was defined with milliseconds precision using Entity Framework Code First or EF Model First, the expected DateTime(n) column did not include the precision specification. (Bug #15972773)

Specifying the Default Command Timeout option in a connection string used with the MySQL Entity Framework provider had no effect. The command timeout was always 30 seconds. (Bug #14825670, Bug #67171)

A System.InvalidCastException exception could occur when calling a stored function. A workaround was to specify the CheckParameters=false connection option. (Bug #13864627, Bug #64633)

Functionality Added or Changed

Bugs Fixed

The medium trust support using the MySQLClientPermissions class is now more flexible: in addition to the original deployment method, where the library is installed in the Global Assembly Cache (GAC), you can also install the library within a bin or lib folder inside the project or solution. When the library is deployed somewhere other than the GAC, the only protocol supported is TCP/IP. Existing applications that use the library installed in the GAC must now include an extra connection option, includesecurityasserts=true. For details, see Working with Partial Trust / Medium Trust. (Bug #14668820, Bug #65036)

Performance: The LINQ to SQL data provider for MySQL was generating inefficient code for the Contains() method, producing a query with multiple OR clauses instead of the more efficient IN clause. (Bug #14016344, Bug #64934)

Performance: The LINQ to SQL data provider for MySQL was generating inefficient code for the StartsWith() and Contains() methods, calling the MySQL LOCATE() function rather than using a LIKE operator with a % wildcard. The fix causes both methods to use the LIKE syntax, although only StartsWith() gains a substantial performance improvement. Queries involving the StartsWith() method can now take advantage of an index on the corresponding column. (Bug #14009363, Bug #64935)

Calling the method FirstOrDefault “LINQ to Entities” queries caused a System.Data.EntityCommandCompilationException exception. (Bug #15856964, Bug #67377)

When using Entity Frameworks: Code First in Visual Studio 2012 and using a GUID as the primary key in a class, the following error could occur:

Incorrect column specifier for column 'column_name'.

Connector/Net was applying the AUTO_INCREMENT attribute to the column, which requires that the column use an integer data type. (Bug #15834176, Bug #67450)

Connection attempts using IPV6 addresses in Connector/Net would fail. (Bug #14835718, Bug #67253)

Visual Studio 2012 projects could sometimes give the following error dialog:

Failed to merge object(s).

Keyword not supported.
Parameter name: AttachDbFilename.

This issue affected mostly VisualStudio 2012 projects, either migrated from VisualStudio 2010 or including web sites created with VS2010, connecting to a MySQL 5.5 server. (Bug #14733472, Bug #66880)

When an application starts up, creates a connection, and then goes idle after a single database operation, the connections are now cleaned up more quickly: typically after an idle time of 3 minutes rather than 6 minutes. This optimization is especially useful for ASP.net applications on low-traffic sites. (Bug #14652624, Bug #66472)

Under some circumstances, setting CacheServerProperties=true in the connection string could cause a Packet too large error. With connection pooling enabled and CacheServerProperties=true, the first connection worked as expected, but the second, third, and so on connections failed if the query exceeded 1024 bytes. (Bug #14593547, Bug #66578)

Connector/Net did not support creating an entity with a key of type string. During database creation, a MySqlException was thrown saying BLOB/TEXT column 'Name' used in key specification without a key length. The DDL produced by the provider specified a MEDIUMTEXT column for the primary key without specifying a length for the key. This fix is particularly important when working with Entity Framework versions 4.3 and later, since the __MigrationsHitory table (which replaces the EdmMetadata table) uses a string property as its key. (Bug #14540202, Bug #65289, Bug #64288)

The ExecuteNonQuery() could return an error Parameter '?' must be defined, when attempting to execute a statement such as:

insert into table_name (Field1, Field1) VALUES(?,?)

That is, when referencing the same field twice with two different ? placeholders. (Bug #14499549, Bug #66060)

When using a MySQL database set up as UTF32 as an ASP.net membership database, web applications could give a “key too long” error, and the Website Administration Tool would not connect to providers. The cause was that the column my_aspnet_sessions.SessionId, when converted from Latin1 character set to UTF32 with 4 bytes per character, exceeded the length limit for a primary key:

Specified key was too long; max key length is 767 bytes

(Bug #14495292, Bug #65144)

The MySQL Connector/Net EntityFramework provider would throw NullReferenceException when trying to insert a new record with an empty VALUES clause. Such an INSERT should work when the only required (NOT NULL) column in the table is a primary key auto-increment column. (Bug #14479715, Bug #66066)

Using the Entity Data Model Designer decimal type and CreateDatabase function, the values were stored with 0 digits at the right of the decimal point. With this fix, the default is 2 digits to the right of the decimal point, and any precision specified through the Entity Data Model Designer is applied correctly. (Bug #14474342, Bug #65127)

Customizing precision by calling the HasPrecision() method within the OnModelCreating() method in a Code First project would always produce precision settings (10,2) rather than the specified precision. (Bug #14469048, Bug #65001)

When building commands through the MySql.Data.MySqlClient.MySqlCommand() class, memory could be leaked because some IO.MemoryStream instances were not being freed efficiently. The memory leak could be an issue in SQL-heavy applications, for example a logging application processing large numbers of INSERT statements. (Bug #14468204, Bug #65696)

When using the ASP.net web security functionality with a MySQL database, using features that access the my_aspnet_usersinroles table caused an exception:

MySql.Data.MySqlClient.MySqlException: Table 'testdb.my_aspnet_usersinrole' doesn't exist.

For example, this error could occur when trying to remove the user from a role or find users in a role. The fix corrects the spelling of the table name to my_aspnet_usersinroles. (Bug #14405338, Bug #65805)

Although the member variable MySqlCommand.LastInsertedId was a 64-bit long, its value was effectively capped at the maximum value of Int32 (2,147,483,647). If a primary key exceeded this value, the value of LastInsertedId was wrong. This mismatch could be an issue for tables with large numbers of rows. (Bug #14171960, Bug #65452)

When using Entity Framework with Connector/Net, the association property OnDelete was not taken into account in the CreateDatabaseScript function of the ObjectContext, leading to an error message System.Data.UpdateException was unhandled. The SQL generated by the CreateDatabaseScript function was missing ON DELETE and ON UPDATE clauses. These clauses were filled in correctly by the DDL generation wizard. (Bug #14008752, Bug #64779)

A call to a stored procedure or function in an application using the Code First entity framework could result in an error:

Unhandled Exception: MySql.Data.MySqlClient.MySqlException: You have an error
in your SQL syntax; ...

The code change allows syntax such as the following to invoke a stored procedure, without using the CALL statement and without using CommandType.StoredProcedure.

int count = myContext.Database.SqlQuery<int>("GetCount").First();

(Bug #14008699, Bug #64999)

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)

When using the Entity Framework Code First approach, the generated code could be incorrect:

(Bug #13900091, Bug #64216)

The milliseconds portion of a date/time value was not stored correctly for the datatype DATETIME(3). (Bug #13881444, Bug #64686)

When using the MySqlProfileProvider, calling the function ProfileManager.DeleteProfiles could throw an InvalidCastException exception. (Bug #13790123, Bug #64470)

A timing issue with the GetItemExclusive, SetAndReleaseItemExclusive, and GetItem functions could cause an application to freeze for almost 2 minutes if GetItem was called at a particular moment when a session was already locked as read-only. (Bug #13733054, Bug #63997)

In Visual Studio Table Designer, the name of a new index was always derived from the name of the table and could not be changed. (Bug #13613801)

When using the Entity Framework Code First approach, the generated code could be use the MEDIUMTEXT data type in contexts where other types such as VARCHAR were more appropriate, leading to errors such as:

error 0064: Facet 'MaxLength' must not be specified for type 'mediumtext'.

(Bug #13582335, Bug #63920)

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 2005, adding a new data connection through the Server Explorer produced an error message: Package Load Failure. The Visual Studio plugin was dynamically linked against VS2008 version of assembly Microsoft.VisualStudio.Data (v9.0). The fixed plugin links with the VS2005 version (v8.0) of that library instead, which is upward compatible with later Visual Studio versions. (Bug #13491674, Bug #63073)

Formerly, cleanup operations for expired sessions were fully automatic, with no ability to catch the timeout event and do application-specific cleanup. This fix adds a enableSessionExpireCallback connection option to let developers catch the event when a session expires. When enableSessionExpireCallback is enabled, the global.asax.session_end event is raised before data is deleted from the my_aspnet_sessions table. When enableSessionExpireCallback is disabled, the data is deleted from the my_aspnet_sessions table without raising the event first. The timeout period for session expiry is specified in the web.config file, in the timeout option of the sessionState section. (Bug #13354935, Bug #62266)

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, 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, modifying the Columns field in the Indexes/Keys dialog multiple times could cause an error. (Bug #13613765)

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

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

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)

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

Creating a trigger on a table using the Server Explorer tree could produce an error message:

Object reference not set to an instance of an object.

(Bug #13511801)

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)

Functionality Added or Changed

Bugs Fixed

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

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

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 Working with Partial Trust / Medium Trust.

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

Added better IntelliSense support, including auto-completion when editing stored procedures or .mysql files.

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)

Calling the method FirstOrDefault “LINQ to Entities” queries caused a System.Data.EntityCommandCompilationException exception. (Bug #15856964, Bug #67377)

When using Entity Frameworks: Code First in Visual Studio 2012 and using a GUID as the primary key in a class, the following error could occur:

Incorrect column specifier for column 'column_name'.

Connector/Net was applying the AUTO_INCREMENT attribute to the column, which requires that the column use an integer data type. (Bug #15834176, Bug #67450)

Connection attempts using IPV6 addresses in Connector/Net would fail. (Bug #14835718, Bug #67253)

Visual Studio 2012 projects could sometimes give the following error dialog:

Failed to merge object(s).

Keyword not supported.
Parameter name: AttachDbFilename.

This issue affected mostly VisualStudio 2012 projects, either migrated from VisualStudio 2010 or including web sites created with VS2010, connecting to a MySQL 5.5 server. (Bug #14733472, Bug #66880)

When an application starts up, creates a connection, and then goes idle after a single database operation, the connections are now cleaned up more quickly: typically after an idle time of 3 minutes rather than 6 minutes. This optimization is especially useful for ASP.net applications on low-traffic sites. (Bug #14652624, Bug #66472)

Under some circumstances, setting CacheServerProperties=true in the connection string could cause a Packet too large error. With connection pooling enabled and CacheServerProperties=true, the first connection worked as expected, but the second, third, and so on connections failed if the query exceeded 1024 bytes. (Bug #14593547, Bug #66578)

Connector/Net did not support creating an entity with a key of type string. During database creation, a MySqlException was thrown saying BLOB/TEXT column 'Name' used in key specification without a key length. The DDL produced by the provider specified a MEDIUMTEXT column for the primary key without specifying a length for the key. This fix is particularly important when working with Entity Framework versions 4.3 and later, since the __MigrationsHitory table (which replaces the EdmMetadata table) uses a string property as its key. (Bug #14540202, Bug #65289, Bug #64288)

The ExecuteNonQuery() could return an error Parameter '?' must be defined, when attempting to execute a statement such as:

insert into table_name (Field1, Field1) VALUES(?,?)

That is, when referencing the same field twice with two different ? placeholders. (Bug #14499549, Bug #66060)

When using a MySQL database set up as UTF32 as an ASP.net membership database, web applications could give a “key too long” error, and the Website Administration Tool would not connect to providers. The cause was that the column my_aspnet_sessions.SessionId, when converted from Latin1 character set to UTF32 with 4 bytes per character, exceeded the length limit for a primary key:

Specified key was too long; max key length is 767 bytes

(Bug #14495292, Bug #65144)

The MySQL Connector/Net EntityFramework provider would throw NullReferenceException when trying to insert a new record with an empty VALUES clause. Such an INSERT should work when the only required (NOT NULL) column in the table is a primary key auto-increment column. (Bug #14479715, Bug #66066)

Using the Entity Data Model Designer decimal type and CreateDatabase function, the values were stored with 0 digits at the right of the decimal point. With this fix, the default is 2 digits to the right of the decimal point, and any precision specified through the Entity Data Model Designer is applied correctly. (Bug #14474342, Bug #65127)

Customizing precision by calling the HasPrecision() method within the OnModelCreating() method in a Code First project would always produce precision settings (10,2) rather than the specified precision. (Bug #14469048, Bug #65001)

When building commands through the MySql.Data.MySqlClient.MySqlCommand() class, memory could be leaked because some IO.MemoryStream instances were not being freed efficiently. The memory leak could be an issue in SQL-heavy applications, for example a logging application processing large numbers of INSERT statements. (Bug #14468204, Bug #65696)

When using the ASP.net web security functionality with a MySQL database, using features that access the my_aspnet_usersinroles table caused an exception:

MySql.Data.MySqlClient.MySqlException: Table 'testdb.my_aspnet_usersinrole' doesn't exist.

For example, this error could occur when trying to remove the user from a role or find users in a role. The fix corrects the spelling of the table name to my_aspnet_usersinroles. (Bug #14405338, Bug #65805)

Although the member variable MySqlCommand.LastInsertedId was a 64-bit long, its value was effectively capped at the maximum value of Int32 (2,147,483,647). If a primary key exceeded this value, the value of LastInsertedId was wrong. This mismatch could be an issue for tables with large numbers of rows. (Bug #14171960, Bug #65452)

When using Entity Framework with Connector/Net, the association property OnDelete was not taken into account in the CreateDatabaseScript function of the ObjectContext, leading to an error message System.Data.UpdateException was unhandled. The SQL generated by the CreateDatabaseScript function was missing ON DELETE and ON UPDATE clauses. These clauses were filled in correctly by the DDL generation wizard. (Bug #14008752, Bug #64779)

A call to a stored procedure or function in an application using the Code First entity framework could result in an error:

Unhandled Exception: MySql.Data.MySqlClient.MySqlException: You have an error
in your SQL syntax; ...

The code change allows syntax such as the following to invoke a stored procedure, without using the CALL statement and without using CommandType.StoredProcedure.

int count = myContext.Database.SqlQuery<int>("GetCount").First();

(Bug #14008699, Bug #64999)

When using the Entity Framework Code First approach, the generated code could be incorrect:

(Bug #13900091, Bug #64216)

A System.InvalidCastException exception could occur when calling a stored function. A workaround was to specify the CheckParameters=false connection option. (Bug #13864627, Bug #64633)

When using the MySqlProfileProvider, calling the function ProfileManager.DeleteProfiles could throw an InvalidCastException exception. (Bug #13790123, Bug #64470)

In Visual Studio Table Designer, the name of a new index was always derived from the name of the table and could not be changed. (Bug #13613801)

When using the Entity Framework Code First approach, the generated code could be use the MEDIUMTEXT data type in contexts where other types such as VARCHAR were more appropriate, leading to errors such as:

error 0064: Facet 'MaxLength' must not be specified for type 'mediumtext'.

(Bug #13582335, Bug #63920)

In Visual Studio 2005, adding a new data connection through the Server Explorer produced an error message: Package Load Failure. The Visual Studio plugin was dynamically linked against VS2008 version of assembly Microsoft.VisualStudio.Data (v9.0). The fixed plugin links with the VS2005 version (v8.0) of that library instead, which is upward compatible with later Visual Studio versions. (Bug #13491674, Bug #63073)

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

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)

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)

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

Creating a trigger on a table using the Server Explorer tree could produce an error message:

Object reference not set to an instance of an object.

(Bug #13511801)

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)

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)

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)

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)

In Table Designer for Visual Studio, trying to create a table could fail if you saved changes immediately after entering the data type for a column. The workaround was to click somewhere else in the grid before saving changes. (Bug #13477805)

Creating a table through the Server Explorer Window on Visual Studio 2010 could fail with a MySQL syntax error. The properties in the CREATE TABLE statement could be listed in incorrect order. (Bug #13475830)

Formerly, cleanup operations for expired sessions were fully automatic, with no ability to catch the timeout event and do application-specific cleanup. This fix adds a enableSessionExpireCallback connection option to let developers catch the event when a session expires. When enableSessionExpireCallback is enabled, the global.asax.session_end event is raised before data is deleted from the my_aspnet_sessions table. When enableSessionExpireCallback is disabled, the data is deleted from the my_aspnet_sessions table without raising the event first. The timeout period for session expiry is specified in the web.config file, in the timeout option of the sessionState section. (Bug #13354935, Bug #62266)

Connector/NET experienced poor performance when adding parameters to the MySQLCommand. (Bug #62653, Bug #13331475)

The Unicode quotation mark character U+0022 was not escaped by the MySQLHelper class. (Bug #62585, Bug #13092886)

Using a return parameter without a name resulted in an IndexOutOfRangeException exception. (Bug #62416, Bug #13006969)

Connector/NET would incorrectly map decimal values to ANSI strings. (Bug #62246, Bug #13050570)

The Mono runtime did not support hashed passwords. (Bug #62203, Bug #13041618)

Connector/NET incorrectly maps PrimitiveTypeKind.Byte to tinyint, instead of utinyint. And PrimitiveTypeKind.SByte mapping was added, to tinyint. (Bug #62135, Bug #13061713)

Functionality Added or Changed

Bugs Fixed

Connector/Net now enables clients to connect to the server through accounts that use Windows native authentication. For more information, see Using the Windows Native Authentication Plugin and The Windows Native Authentication Plugin.

(Bug #12897149)

When creating a tableadapter through a Dataset form in Visual Studio, the MaxLength of the field for a CHAR column could be set to 3 times the length of the table column. Although this many bytes could be needed to hold a UTF-8 character value, the length value was not appropriate for restricting the length of a TextBox. (Bug #12860224, Bug #62094)

An error out of sync with server could occur when connecting in the Visual Studio Entity Framework. The issue occurred only on some MySQL servers, all with versions earlier than MySQL 5.5. (Bug #12853286, Bug #61806)

When adding a MEDIUMTEXT or LONGTEXT column Visual Studio, the facet Fixed length had to be set to false, even though these types allow arbitrary lengths. (Bug #12848277, Bug #54915)

Executing a “LINQ to Entity” query could result in a NullReferenceException error. (Bug #12776598, Bug #61729)

Using a combination of ListView, EntityDataSource with TypeFilter and Include EntityCollection Navigation Property, and DataPager caused a NullReferenceException error in the System.Web.UI.WebControls.EntityDataSourceView.ExecuteSelect function. (Bug #12776517, Bug #61714)

MySqlDataReader.Close was modified to use Default behavior when clearing remaining result sets. (Bug #61690, Bug #12723423)

MySqlScript was modified to enable correct processing of the DELIMITER command when not followed by a new line. (Bug #61680, Bug #12732279)

The ASP.NET membership provider was modified to create and query all related tables using lowercase names. (Bug #61108, Bug #12702009)

On Model First changed column types generated in SQL scripts to produce more suitable MySql types. (Bug #59244, Bug #12707104)

SchemaDefinition-5.5.ssdl was modified to treat CHAR(36) columns as a GUID. (Bug #61657, Bug #12708208)

SqlFragment.QuoteIdentifier was modified to add MySQL quotes around identifiers. (Bug #61635, Bug #12707285)

Modified MySqlConnection.BeginTransaction to throw a NotSupportedException for Snapshot isolation level. (Bug #61589, Bug #12698020)

Modified ProviderManifest.xml to map TIMESTAMP database columns to the DateTime .NET type. (Bug #55351, Bug #12652602)

Fixed Entity Framework provider GROUP BY clause generation by adding all group-by keys to the SELECT statement. (Bug #46742, Bug #12622129)

Calling a stored procedure with output parameters caused a marked performance decrease. (Bug #60366, Bug #12425959)

Changed how the procedure schema collection is retrieved. If the connection string contains “use procedure bodies=true” then a SELECT is performed on the mysql.proc table directly, as this is up to 50 times faster than the current Information Schema implementation. If the connection string contains “use procedure bodies=false”, then the Information Schema collection is queried. (Bug #36694)

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)

When adding a ADO.NET Entity Data Model and generating the model from a database containing foreign keys, the foreign keys were not included in the generated model. (Bug #13800109)

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)

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, 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, 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, modifying the Columns field in the Indexes/Keys dialog multiple times could cause an error. (Bug #13613765)

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

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

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)

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

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)

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

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

Creating a trigger on a table using the Server Explorer tree could produce an error message:

Object reference not set to an instance of an object.

(Bug #13511801)

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

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)

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)

The class MySql.Data.Types.MySqlDateTime was not serializable. (Bug #11750161, Bug #40555)

Connector/NET would incorrectly map decimal values to ANSI strings. (Bug #62246, Bug #13050570)

Connector/NET incorrectly maps PrimitiveTypeKind.Byte to tinyint, instead of utinyint. And PrimitiveTypeKind.SByte mapping was added, to tinyint. (Bug #62135, Bug #13061713)

On Model First changed column types generated in SQL scripts to produce more suitable MySql types. (Bug #59244, Bug #12707104)

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)

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)

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 columns added in descending sort order were not included in the index, as defined within the Server Explorer. (Bug #13481709)

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)

When creating a foreign key relationship in Table Designer, changes to the ON UPDATE and ON CASCADE settings were not reflected in the actual table definition, as displayed by SHOW CREATE TABLE. (Bug #13481348)

In table designer for Visual Studio, you could not create a foreign key that referenced the same table as source and destination. When adding a new relationship, the Referenced table list did not offer the original table as one of the choices. (Bug #13481340)

The comment property and index type were not added in the definition of the index, as defined within the Server Explorer. (Bug #13481314)

Removing a method was not affecting the indexes list of the table object, as defined within the Table Designer. (Bug #13481313)

When a new column was added in Table Designer without selecting an associated data type, an error would occur trying to save the column definition. (Bug #13481298)

Creating a table through the Server Explorer Window on Visual Studio 2010 could fail with a MySQL syntax error. The properties in the CREATE TABLE statement could be listed in incorrect order. (Bug #13475830)

The Connector/Net installed for all users, and thus was not available in the Add/Remove Programs dialog for users other than the one who installed it. (Bug #13447941)

The default value for VARCHAR and CHAR field types would contain single quotation marks. (Bug #13442506)

When creating a tableadapter through a Dataset form in Visual Studio, the MaxLength of the field for a CHAR column could be set to 3 times the length of the table column. Although this many bytes could be needed to hold a UTF-8 character value, the length value was not appropriate for restricting the length of a TextBox. (Bug #12860224, Bug #62094)

When adding a MEDIUMTEXT or LONGTEXT column Visual Studio, the facet Fixed length had to be set to false, even though these types allow arbitrary lengths. (Bug #12848277, Bug #54915)

Executing a “LINQ to Entity” query could result in a NullReferenceException error. (Bug #12776598, Bug #61729)

Using a combination of ListView, EntityDataSource with TypeFilter and Include EntityCollection Navigation Property, and DataPager caused a NullReferenceException error in the System.Web.UI.WebControls.EntityDataSourceView.ExecuteSelect function. (Bug #12776517, Bug #61714)

Connector/NET experienced poor performance when adding parameters to the MySQLCommand. (Bug #62653, Bug #13331475)

The Unicode quotation mark character U+0022 was not escaped by the MySQLHelper class. (Bug #62585, Bug #13092886)

Using a return parameter without a name resulted in an IndexOutOfRangeException exception. (Bug #62416, Bug #13006969)

The Mono runtime did not support hashed passwords. (Bug #62203, Bug #13041618)

MySqlDataReader.Close was modified to use Default behavior when clearing remaining result sets. (Bug #61690, Bug #12723423)

MySqlScript was modified to enable correct processing of the DELIMITER command when not followed by a new line. (Bug #61680, Bug #12732279)

SchemaDefinition-5.5.ssdl was modified to treat CHAR(36) columns as a GUID. (Bug #61657, Bug #12708208)

SqlFragment.QuoteIdentifier was modified to add MySQL quotes around identifiers. (Bug #61635, Bug #12707285)

Modified MySqlConnection.BeginTransaction to throw a NotSupportedException for Snapshot isolation level. (Bug #61589, Bug #12698020)

The ASP.NET membership provider was modified to create and query all related tables using lowercase names. (Bug #61108, Bug #12702009)

Modified ProviderManifest.xml to map TIMESTAMP database columns to the DateTime .NET type. (Bug #55351, Bug #12652602)

Functionality Added or Changed

Bugs Fixed

Calling a stored procedure with output parameters caused a marked performance decrease. (Bug #60366, Bug #12425959)

MySQLConnectionStringBuilder.ContainsKey() incorrectly returned false when testing whether a keyword was part of the connection string. (Bug #11766671, Bug #59835)

MySQL Connector/Net 6.3.6 did not work with Visual Studio 2010. (Bug #60723, Bug #12394470)

MysqlDataReader.GetSchemaTable returned incorrect values and types. (Bug #59989, Bug #11776346)

All queries other than INSERT were executed individually instead of as a batch even though batching was enabled for the connection. (Bug #59616, Bug #11850286)

MySQL Connector/Net generated an exception when executing a query consisting of ';', for example:

mycmd(";",mycon)
mycmd.executenonquery()

The exception generated was:

System.IndexOutOfRangeException: Index was outside the bounds of the array.
   at MySql.Data.MySqlClient.MySqlCommand.TrimSemicolons(String sql)
   at MySql.Data.MySqlClient.MySqlCommand.ExecuteReader(CommandBehavior behavior)
   at MySql.Data.MySqlClient.MySqlCommand.ExecuteReader()
   at MySql.Data.MySqlClient.MySqlCommand.ExecuteNonQuery()

(Bug #59537, Bug #11766433)

Setting Membership.ApplicationName had no effect. (Bug #59438, Bug #11770465)

A NullReferenceException was thrown on disposal of a TransactionScope object. (Bug #59346, Bug #11766272)

The setup wizard failed with the error “Setup Wizard ended prematurely because of an error”. This was because it assumed .NET Framework version 4.0 was located on the C: drive, when it was actually located on the E: drive. (Bug #59301)

Fixed Entity Framework provider GROUP BY clause generation by adding all group-by keys to the SELECT statement. (Bug #46742, Bug #12622129)

Functionality Added or Changed

Bugs Fixed

Changed how the procedure schema collection is retrieved. If the connection string contains “use procedure bodies=true” then a SELECT is performed on the mysql.proc table directly, as this is up to 50 times faster than the current Information Schema implementation. If the connection string contains “use procedure bodies=false”, then the Information Schema collection is queried. (Bug #36694)

MembershipProvider did not generate hashes correctly if the algorithm was keyed. The Key of the algorithm should have been set if the HashAlgorithm was KeyedHashAlgorithm. (Bug #58906)

Code introduced to fix bug #54863 proved problematic on .NET version 3.5 and above. (Bug #58853)

The MySqlTokenizer contained unnecessary Substring and Trim calls:

string token = sql.Substring(startIndex, stopIndex - startIndex).Trim();

The variable token was not used anywhere in the code. (Bug #58757)

MySqlCommand.ExecuteReader(CommandBehavior) threw a NullReferenceException when being called with CommandBehavior.CloseConnection, if the SQL statement contained a syntax error, or contained invalid data such as an invalid column name. (Bug #58652)

ReadFieldLength() returned incorrect value for BIGINT autoincrement columns. (Bug #58373)

When attempting to create an ADO.NET Entity Data Model, MySQL connections were not available. (Bug #58278)

MySQL Connector/Net did not support the utf8mb4 character set. When attempting to connect to utf8mb4 tables or columns, an exception KeyNotFoundException was generated. (Bug #58244)

Installation of MySQL Connector/Net 6.3.5 failed. The error reported was:

MySQL Connector Net 6.3.5 Setup Wizard ended
prematurely because of an error. Your system has not been modified.

(Bug #57654)

When the tracing driver was used and an SQL statement was longer than 300 characters, an ArgumentOutOfRangeExcpetion occurred if the statement also contained a quoted character, and the 300th character was in the middle of a quoted token. (Bug #57641)

Calling the Read() method on a DataReader obtained from MySqlHelper.ExecuteReader generated the following exception:

Unhandled Exception: MySql.Data.MySqlClient.MySqlException: Invalid attempt to R
ead when reader is closed.
   at MySql.Data.MySqlClient.MySqlDataReader.Read()
   at MySqlTest.MainClass.Main(String[] args)

(Bug #57501)

Default values returned for text columns were not quoted. This meant that the COLUMN_DEFAULT field of the GetSchema columns collection did not return a valid SQL expression. (Bug #56509)

When using MySQL Connector/Net on Mono 2.8 using .NET 4.0, attempting to connect to a MySQL database generated the following exception:

Unhandled Exception: System.MissingMethodException: Method not found:
 'System.Data.Common.DbConnection.EnlistTransaction'.
  at (wrapper remoting-invoke-with-check)
 MySql.Data.MySqlClient.MySqlConnection:Open ()

(Bug #56509)

MySQL Connector/Net for .NET/Mono attempted to dynamically load the assembly Mono.Posix.dll when a Unix socket was used to connect to the server. This failed and the connector was not able to use a Unix socket unless the Mono.Posix.dll assembly was previously loaded by the program. (Bug #56410)

The ADO.NET Entity Data Model could not add stored procedures from MySQL Server 5.0.45 but worked fine using MySQL Server 5.1. (Bug #55349)

In the ADO.NET Entity Data Model Wizard, the time to update a model scaled abnormally as the number of entities increased. (Bug #48791, Bug #12596237)

A typed dataset did not get the table name. (Bug #57894, Bug #11764989)

Setting MySqlCommand.CommandTimeout to 0 had no effect. It should have resulted in an infinite timeout. (Bug #57265)

When performing a row-by-row update, only the first row was updated and all other rows were ignored. (Bug #57092)

MySQL Connector/Net experienced two problems as follows:

(Bug #56859)

Setting the Default Command Timeout connection string option had no effect. (Bug #56806)

When an output parameter was declared as type MySqlDbType.Bit, it failed to return with the correct value. (Bug #56756)

MySqlHelper.ExecuteReader did not include an overload accepting MySqlParameter objects when using a MySqlConnection. However, MySqlHelper did include an overload for MySqlParameter objects when using a string object containing the connection string to the database. (Bug #56755)

MySQL Connector/Net 6.1.3 (GA) would not install on a Windows Server 2008 (Web Edition) clean installation. There were two problems:

(Bug #56580)

The calculation of lockAge in the Session Provider sometimes generated a System.Data.SqlTypes.SqlNullValueException. (Bug #55701)

Attempting to read Double.MinValue from a DOUBLE column in MySQL table generated the following exception:

System.OverflowException : Value was either too large or too small for a Double.

--OverflowException
at System.Number.ParseDouble(String value, NumberStyles options, NumberFormatInfo
numfmt)
at MySql.Data.Types.MySqlDouble.MySql.Data.Types.IMySqlValue.ReadValue(MySqlPacket
packet, Int64 length, Boolean nullVal)
at MySql.Data.MySqlClient.NativeDriver.ReadColumnValue(Int32 index, MySqlField field,
IMySqlValue valObject)
at MySql.Data.MySqlClient.ResultSet.ReadColumnData(Boolean outputParms)
at MySql.Data.MySqlClient.ResultSet.NextRow(CommandBehavior behavior)
at MySql.Data.MySqlClient.MySqlDataReader.Read()

(Bug #55644)

Calling MySqlDataAdapter.Update(DataTable) resulted in an unacceptable performance hit when updating large amounts of data. (Bug #55609)

If using MySQL Server 5.0.x it was not possible to alter stored routines in Visual Studio. If the stored routine was clicked, and the context sensitive menu option, Alter Routine, selected, the following error was generated:

Unable to load object with error: Object reference not
set to an instance of an object

(Bug #55170)

EventLog was not disposed in the SessionState provider. (Bug #52550)

When attempting to carry out an operation such as:

from p in db.Products where p.PostedDate>=DateTime.Now select p;

Where p.PostedDate is a DateTimeOffset, and the underlying column type is a TIMESTAMP, the following exception was generated:

MySqlException occurred
Unable to serialize date/time value

MySQL Connector/Net has now been changed so that all TIMESTAMP columns will be surfaced as DateTime. (Bug #52550)

Stored procedure enumeration code generated an error if a procedure was used in a dataset that did not return any resultsets. (Bug #50671)

The INSERT command was significantly slower with MySQL Connector/Net 6.x compared to 5.x, when compression was enabled. (Bug #48243)

Opening a connection in the Visual Studio Server Explorer and choosing to alter an existing routine required another authentication at the server. (Bug #44715)

MySqlDataAdapter.Update() generated concurrency violations for custom stored procedure driven update commands that used UpdateRowSource.FirstReturnedRecord. (Bug #54895)

Several calls to DataAdapter.Update() with intervening changes to DataTable resulted in ConcurrencyException exceptions being generated. (Bug #54863)

MySQL Connector/Net generated a null reference exception when TransactionScope was used by multiple threads. (Bug #54681)

The icon for the MySQL Web Configuration Tool was not displayed in Visual Studio for Web Application Projects. (Bug #54571)

The MySqlHelper object did not have an overloaded version of the ExecuteReader method that accepted a MySqlConnection object. (Bug #54570)

If MySqlDataAdapter was used with an INSERT command where the VALUES clause contained an expression with parentheses in it, and set the adapter.UpdateBatchSize parameter to be greater than one, then the call to adapter.Update either generated an exception or failed to batch the commands, executing each insert individually. (Bug #54386)

The method MySql.Data.Common.QueryNormalizer.CollapseValueList generated an ArgumentOutOfRangeException. (Bug #54152, Bug #53865)

MySQL Connector/Net did not process Thread.Abort() correctly, and failed to cancel queries currently running on the server. (Bug #54012)

MySQL Connector/Net 6.3.2 failed to install on Windows Vista. (Bug #53975)

Garbage Collector disposal of a MySqlConnection object caused the following exception:

System.IO.EndOfStreamException: Attempted to read past the end of the stream.
MySql.Data.MySqlClient.MySqlStream.ReadFully(Stream stream, Byte[] buffer, Int32 offset,
Int32 count)
MySql.Data.MySqlClient.MySqlStream.LoadPacket()
Outer Exception Reading from the stream has failed.
...

(Bug #53457)

MySQL Connector/Net did not throw an EndOfStreamException exception when net_write_timeout was exceeded. (Bug #53439)

After a timeout exception, if an attempt was made to reuse a connection returned to the connection pool the following exception was generated:

[MySqlException (0x80004005): There is already an open DataReader associated with this
Connection which must be closed first.]
   MySql.Data.MySqlClient.MySqlCommand.CheckState() +278
   MySql.Data.MySqlClient.MySqlCommand.ExecuteReader(CommandBehavior behavior) +43
   MySql.Data.MySqlClient.MySqlCommand.ExecuteReader() +6
   Controls.SimpleCommand.ExecuteReader(String SQL) in ...:323
   Albums.GetImagesByAlbum(SimpleCommand Cmd, Int32 iAlbum, String Order, String Limit)
in ...:13
   Forecast.Page_Load(Object sender, EventArgs e) in ...:70
   System.Web.UI.Control.OnLoad(EventArgs e) +99
   System.Web.UI.Control.LoadRecursive() +50
   System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean
includeStagesAfterAsyncPoint) +627

(Bug #53357)

Membership schema creation failed if the default schema collation was not Latin1. (Bug #53174)

The MySQL Connector/Net installation failed due to machine.config files not being present in configuration folders.

MySQL Connector/Net has been changed to skip over configuration folders that do not contain a machine.config file. (Bug #52352)

CHAR(36) columns were not recognized as GUIDs when used in views with entity models. (Bug #52085)

When an application was subjected to increased concurrent load, MySQL Connector/Net generated the following error when calling stored procedures:

A DataTable named \'Procedure Parameters\'
already belongs to this DataSet.

(Bug #49118)

When the connection string option “Connection Reset = True” was used, a connection reset used the previously used encoding for the subsequent authentication operation. This failed, for example, if UCS2 was used to read the last column before the reset. (Bug #47153)

When batching was used in MySqlDataAdapter, a connection was not opened automatically in MySqlDataAdapter.Update(). This resulted in an InvalidOperationException exception being generated, with the message text “connection must be valid and open”.

MySQL Connector/Net has been changed to behave more like SQL Server: if the connection is closed, it is opened for the duration of update operation. (Bug #38411)

Database name was emitted into typed datasets. This prevented users using the configured default database. (Bug #33870)

Functionality Added or Changed

Bugs Fixed

Procedure caching had a problem whereby if you created a procedure, dropped it, and recreated it with a different number of parameters an exception was generated.

MySQL Connector/Net has been changed so that if the procedure is recreated with a different number of parameters, it will still be recognized. (Bug #52562)

MySQL Connector/Net has been changed to include MySqlDataReader.GetFieldType(string columnname). Further, MySqlDataReader.GetOrdinal() now includes the name of the column in the exception if the column is not found. (Bug #47467)

After an exception, the internal datareader, MySqlCommand.Connection.Reader, was not properly closed (it was not set to null). If another query was subsequently executed on that command object an exception was generated with the message “There is already an open DataReader associated with this Connection which must be closed first.” (Bug #55558)

MySQL Connector/Net generated an exception when used to read a TEXT column containing more than 32767 bytes. (Bug #54040)

In MySQL Connector/Net, the MySqlConnection.Abort() method contained a try...catch construct, with an empty catch block. This meant that any exception generated at this point would not be caught. (Bug #52769)

The procedure cache affected the MySQL Connector/Net performance, reducing it by around 65%. This was due to unnecessary calls of String.Format(), related to debug logging. Even though the logging was disabled the string was still being formatted, resulting in impaired performance. (Bug #52475)

If FunctionsReturnString=true was used in the connection string, the decimal separator (according to locale) was not interpreted. (Bug #52187)

In MySQL Connector/Net, the LoadCharsetMap() function of the CharSetMap class set the following incorrect mapping:

mapping.Add("latin1", new CharacterSet("latin1", 1));

This meant that, for example, the Euro sign was not handled correctly.

The correct mapping should have been:

mapping.Add("latin1", new CharacterSet("windows-1252", 1));

This is because the MySQL latin1 character set is the same as the windows-cp1252 character set and it extends the official ISO 8859-1 or IANA latin1. (Bug #51927)

A non-terminated string in SQL threw a CLR exception rather than a syntax exception. (Bug #51788)

When calling ExecuteNonQuery on a command object, the following exception occurred:

Index and length must refer to a location within the string.
Parameter name: length

(Bug #51610)

MySQL Connector/Net 6.3.1 failed to install. (Bug #51407, Bug #51604)

When using table per type inheritance and listing the contents of the parent table, the result of the query was a list of child objects, even though there was no related child record with the same parent Id. (Bug #49850)

Functionality Added or Changed

Bugs Fixed

Connector/Net was not compatible with Visual Studio wizards that used square brackets to delimit symbols.

Connector/Net has been changed to include a new connection string option Sql Server mode that supports use of square brackets to delimit symbols. (Bug #35852)

Specifying a connection string where an option had no value generated an error, rather than the value being set to the default. For example, a connection string such as the following would result in an error:

server=localhost;user=root;compress=;database=test;port=3306;password=123456;

(Bug #51209)

The method Command.TrimSemicolons used StringBuilder, and therefore allocated memory for the query even if it did not need to be trimmed. This led to excessive memory consumption when executing a number of large queries. (Bug #51149)

MySqlCommand.Parameters.Clear() did not work. (Bug #50444)

Binary Columns were not displayed in the Query Builder of Visual Studio. (Bug #50171)

When the UpdateBatchSize property was set to a value greater than 1, only the first row was applied to the database. (Bug #50123)

When trying to create stored procedures from an SQL script, a MySqlException was thrown when attempting to redefine the DELIMITER:

MySql.Data.MySqlClient.MySqlException was unhandled
Message="You have an error in your SQL syntax; check the manual that corresponds to your
MySQL server version for the right syntax to use near 'DELIMITER' at line 1"
Source="MySql.Data"
ErrorCode=-2147467259
Number=1064
StackTrace:
à MySql.Data.MySqlClient.MySqlStream.ReadPacket()
à MySql.Data.MySqlClient.NativeDriver.ReadResult(UInt64& affectedRows, Int64&
lastInsertId)
à MySql.Data.MySqlClient.MySqlDataReader.GetResultSet()
à MySql.Data.MySqlClient.MySqlDataReader.NextResult()
à MySql.Data.MySqlClient.MySqlCommand.ExecuteReader(CommandBehavior behavior)
à MySql.Data.MySqlClient.MySqlCommand.ExecuteReader()
à MySql.Data.MySqlClient.MySqlCommand.ExecuteNonQuery()
à MySql.Data.MySqlClient.MySqlScript.Execute()

Note: The MySqlScript class has been fixed to support the delimiter statement as it is found in SQL scripts. (Bug #46429)

A connection string set in web.config could not be reused after Visual Studio 2008 Professional was shut down. It continued working for the existing controls, but did not work for new controls added. (Bug #41629)

Functionality Added or Changed

Bugs Fixed

Nested transaction scopes were not supported. MySQL Connector/Net now implements nested transaction scopes. A per-thread stack of scopes is maintained, which is necessary to handle nested scopes with the RequiresNew or Suppress options. (Bug #45098)

Support for MySQL Server 4.1 has been removed from MySQL Connector/Net starting with version 6.3.0. The connector will now throw an exception if you try to connect to a server of version less than 5.0.

When adding a data set in Visual Studio 2008, the following error was generated:

Relations couldn't be added. Column 'REFERENCED_TABLE_CATALOG' does not belong to table.

This was due to a 'REFERENCED_TABLE_CATALOG' column not being included in the foreign keys collection. (Bug #48974)

Attempting to execute a load data local infile on a file where the user did not have write permissions, or the file was open in an editor gave an access denied error. (Bug #48944)

The method MySqlDataReader.GetSchemaTable() returned 0 in the NumericPrecision field for decimal and newdecimal columns. (Bug #48171)

When creating a tableadapter through a Dataset form in Visual Studio, the MaxLength of the field for a CHAR column could be set to 3 times the length of the table column. Although this many bytes could be needed to hold a UTF-8 character value, the length value was not appropriate for restricting the length of a TextBox. (Bug #12860224, Bug #62094)

Executing a “LINQ to Entity” query could result in a NullReferenceException error. (Bug #12776598, Bug #61729)

Using a combination of ListView, EntityDataSource with TypeFilter and Include EntityCollection Navigation Property, and DataPager caused a NullReferenceException error in the System.Web.UI.WebControls.EntityDataSourceView.ExecuteSelect function. (Bug #12776517, Bug #61714)

MySqlScript was modified to enable correct processing of the DELIMITER command when not followed by a new line. (Bug #61680, Bug #12732279)

The ASP.NET membership provider was modified to create and query all related tables using lowercase names. (Bug #61108, Bug #12702009)

On Model First changed column types generated in SQL scripts to produce more suitable MySql types. (Bug #59244, Bug #12707104)

MySQLConnectionStringBuilder.ContainsKey() incorrectly returned false when testing whether a keyword was part of the connection string. (Bug #11766671, Bug #59835)

SchemaDefinition-5.5.ssdl was modified to treat CHAR(36) columns as a GUID. (Bug #61657, Bug #12708208)

SqlFragment.QuoteIdentifier was modified to add MySQL quotes around identifiers. (Bug #61635, Bug #12707285)

Modified MySqlConnection.BeginTransaction to throw a NotSupportedException for Snapshot isolation level. (Bug #61589, Bug #12698020)

MysqlDataReader.GetSchemaTable returned incorrect values and types. (Bug #59989, Bug #11776346)

All queries other than INSERT were executed individually instead of as a batch even though batching was enabled for the connection. (Bug #59616, Bug #11850286)

MySQL Connector/Net generated an exception when executing a query consisting of ';', for example:

mycmd(";",mycon)
mycmd.executenonquery()

The exception generated was:

System.IndexOutOfRangeException: Index was outside the bounds of the array.
   at MySql.Data.MySqlClient.MySqlCommand.TrimSemicolons(String sql)
   at MySql.Data.MySqlClient.MySqlCommand.ExecuteReader(CommandBehavior behavior)
   at MySql.Data.MySqlClient.MySqlCommand.ExecuteReader()
   at MySql.Data.MySqlClient.MySqlCommand.ExecuteNonQuery()

(Bug #59537, Bug #11766433)

Setting Membership.ApplicationName had no effect. (Bug #59438, Bug #11770465)

A NullReferenceException was thrown on disposal of a TransactionScope object. (Bug #59346, Bug #11766272)

MembershipProvider did not generate hashes correctly if the algorithm was keyed. The Key of the algorithm should have been set if the HashAlgorithm was KeyedHashAlgorithm. (Bug #58906)

Code introduced to fix bug #54863 proved problematic on .NET version 3.5 and above. (Bug #58853)

The MySqlTokenizer contained unnecessary Substring and Trim calls:

string token = sql.Substring(startIndex, stopIndex - startIndex).Trim();

The variable token was not used anywhere in the code. (Bug #58757)

MySqlCommand.ExecuteReader(CommandBehavior) threw a NullReferenceException when being called with CommandBehavior.CloseConnection, if the SQL statement contained a syntax error, or contained invalid data such as an invalid column name. (Bug #58652)

ReadFieldLength() returned incorrect value for BIGINT autoincrement columns. (Bug #58373)

MySQL Connector/Net did not support the utf8mb4 character set. When attempting to connect to utf8mb4 tables or columns, an exception KeyNotFoundException was generated. (Bug #58244)

A typed dataset did not get the table name. (Bug #57894, Bug #11764989)

Setting MySqlCommand.CommandTimeout to 0 had no effect. It should have resulted in an infinite timeout. (Bug #57265)

When performing a row-by-row update, only the first row was updated and all other rows were ignored. (Bug #57092)

Setting the Default Command Timeout connection string option had no effect. (Bug #56806)

When an output parameter was declared as type MySqlDbType.Bit, it failed to return with the correct value. (Bug #56756)

MySqlHelper.ExecuteReader did not include an overload accepting MySqlParameter objects when using a MySqlConnection. However, MySqlHelper did include an overload for MySqlParameter objects when using a string object containing the connection string to the database. (Bug #56755)

Default values returned for text columns were not quoted. This meant that the COLUMN_DEFAULT field of the GetSchema columns collection did not return a valid SQL expression. (Bug #56509)

MySQL Connector/Net for .NET/Mono attempted to dynamically load the assembly Mono.Posix.dll when a Unix socket was used to connect to the server. This failed and the connector was not able to use a Unix socket unless the Mono.Posix.dll assembly was previously loaded by the program. (Bug #56410)

Modified ProviderManifest.xml to map TIMESTAMP database columns to the DateTime .NET type. (Bug #55351, Bug #12652602)

The ADO.NET Entity Data Model could not add stored procedures from MySQL Server 5.0.45 but worked fine using MySQL Server 5.1. (Bug #55349)

Fixed Entity Framework provider GROUP BY clause generation by adding all group-by keys to the SELECT statement. (Bug #46742, Bug #12622129)

Functionality Added or Changed

Bugs Fixed

Procedure caching had a problem whereby if you created a procedure, dropped it, and recreated it with a different number of parameters an exception was generated.

MySQL Connector/Net has been changed so that if the procedure is recreated with a different number of parameters, it will still be recognized. (Bug #52562)

The calculation of lockAge in the Session Provider sometimes generated a System.Data.SqlTypes.SqlNullValueException. (Bug #55701)

Attempting to read Double.MinValue from a DOUBLE column in MySQL table generated the following exception:

System.OverflowException : Value was either too large or too small for a Double.

--OverflowException
at System.Number.ParseDouble(String value, NumberStyles options, NumberFormatInfo
numfmt)
at MySql.Data.Types.MySqlDouble.MySql.Data.Types.IMySqlValue.ReadValue(MySqlPacket
packet, Int64 length, Boolean nullVal)
at MySql.Data.MySqlClient.NativeDriver.ReadColumnValue(Int32 index, MySqlField field,
IMySqlValue valObject)
at MySql.Data.MySqlClient.ResultSet.ReadColumnData(Boolean outputParms)
at MySql.Data.MySqlClient.ResultSet.NextRow(CommandBehavior behavior)
at MySql.Data.MySqlClient.MySqlDataReader.Read()

(Bug #55644)

After an exception, the internal datareader, MySqlCommand.Connection.Reader, was not properly closed (it was not set to null). If another query was subsequently executed on that command object an exception was generated with the message “There is already an open DataReader associated with this Connection which must be closed first.” (Bug #55558)

If using MySQL Server 5.0.x it was not possible to alter stored routines in Visual Studio. If the stored routine was clicked, and the context sensitive menu option, Alter Routine, selected, the following error was generated:

Unable to load object with error: Object reference not
set to an instance of an object

(Bug #55170)

MySqlDataAdapter.Update() generated concurrency violations for custom stored procedure driven update commands that used UpdateRowSource.FirstReturnedRecord. (Bug #54895)

Several calls to DataAdapter.Update() with intervening changes to DataTable resulted in ConcurrencyException exceptions being generated. (Bug #54863)

The icon for the MySQL Web Configuration Tool was not displayed in Visual Studio for Web Application Projects. (Bug #54571)

The MySqlHelper object did not have an overloaded version of the ExecuteReader method that accepted a MySqlConnection object. (Bug #54570)

If MySqlDataAdapter was used with an INSERT command where the VALUES clause contained an expression with parentheses in it, and set the adapter.UpdateBatchSize parameter to be greater than one, then the call to adapter.Update either generated an exception or failed to batch the commands, executing each insert individually. (Bug #54386)

The method MySql.Data.Common.QueryNormalizer.CollapseValueList generated an ArgumentOutOfRangeException. (Bug #54152, Bug #53865)

MySQL Connector/Net did not process Thread.Abort() correctly, and failed to cancel queries currently running on the server. (Bug #54012)

Garbage Collector disposal of a MySqlConnection object caused the following exception:

System.IO.EndOfStreamException: Attempted to read past the end of the stream.
MySql.Data.MySqlClient.MySqlStream.ReadFully(Stream stream, Byte[] buffer, Int32 offset,
Int32 count)
MySql.Data.MySqlClient.MySqlStream.LoadPacket()
Outer Exception Reading from the stream has failed.
...

(Bug #53457)

MySQL Connector/Net did not throw an EndOfStreamException exception when net_write_timeout was exceeded. (Bug #53439)

After a timeout exception, if an attempt was made to reuse a connection returned to the connection pool the following exception was generated:

[MySqlException (0x80004005): There is already an open DataReader associated with this
Connection which must be closed first.]
   MySql.Data.MySqlClient.MySqlCommand.CheckState() +278
   MySql.Data.MySqlClient.MySqlCommand.ExecuteReader(CommandBehavior behavior) +43
   MySql.Data.MySqlClient.MySqlCommand.ExecuteReader() +6
   Controls.SimpleCommand.ExecuteReader(String SQL) in ...:323
   Albums.GetImagesByAlbum(SimpleCommand Cmd, Int32 iAlbum, String Order, String Limit)
in ...:13
   Forecast.Page_Load(Object sender, EventArgs e) in ...:70
   System.Web.UI.Control.OnLoad(EventArgs e) +99
   System.Web.UI.Control.LoadRecursive() +50
   System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean
includeStagesAfterAsyncPoint) +627

(Bug #53357)

Membership schema creation failed if the default schema collation was not Latin1. (Bug #53174)

In MySQL Connector/Net, the MySqlConnection.Abort() method contained a try...catch construct, with an empty catch block. This meant that any exception generated at this point would not be caught. (Bug #52769)

EventLog was not disposed in the SessionState provider. (Bug #52550)

The procedure cache affected the MySQL Connector/Net performance, reducing it by around 65%. This was due to unnecessary calls of String.Format(), related to debug logging. Even though the logging was disabled the string was still being formatted, resulting in impaired performance. (Bug #52475)

If FunctionsReturnString=true was used in the connection string, the decimal separator (according to locale) was not interpreted. (Bug #52187)

Periodically the session provider threw an SqlNullValueException exception. When this happened, the row within the my_aspnet_Sessions table had locked always set to '1'. The locked status never changed back to '0' and the user experienced the exception on every page, until their browser was closed and reopened (recreating a new sessionID), or the locked value was manually changed to '0'. (Bug #52175)

CHAR(36) columns were not recognized as GUIDs when used in views with entity models. (Bug #52085)

In MySQL Connector/Net, the LoadCharsetMap() function of the CharSetMap class set the following incorrect mapping:

mapping.Add("latin1", new CharacterSet("latin1", 1));

This meant that, for example, the Euro sign was not handled correctly.

The correct mapping should have been:

mapping.Add("latin1", new CharacterSet("windows-1252", 1));

This is because the MySQL latin1 character set is the same as the windows-cp1252 character set and it extends the official ISO 8859-1 or IANA latin1. (Bug #51927)

Stored procedure enumeration code generated an error if a procedure was used in a dataset that did not return any resultsets. (Bug #50671)

When an application was subjected to increased concurrent load, MySQL Connector/Net generated the following error when calling stored procedures:

A DataTable named \'Procedure Parameters\'
already belongs to this DataSet.

(Bug #49118)

In the ADO.NET Entity Data Model Wizard, the time to update a model scaled abnormally as the number of entities increased. (Bug #48791, Bug #12596237)

The INSERT command was significantly slower with MySQL Connector/Net 6.x compared to 5.x, when compression was enabled. (Bug #48243)

When the connection string option “Connection Reset = True” was used, a connection reset used the previously used encoding for the subsequent authentication operation. This failed, for example, if UCS2 was used to read the last column before the reset. (Bug #47153)

Opening a connection in the Visual Studio Server Explorer and choosing to alter an existing routine required another authentication at the server. (Bug #44715)

When batching was used in MySqlDataAdapter, a connection was not opened automatically in MySqlDataAdapter.Update(). This resulted in an InvalidOperationException exception being generated, with the message text “connection must be valid and open”.

MySQL Connector/Net has been changed to behave more like SQL Server: if the connection is closed, it is opened for the duration of update operation. (Bug #38411)

Database name was emitted into typed datasets. This prevented users using the configured default database. (Bug #33870)

Functionality Added or Changed

Bugs Fixed

MySQL Connector/Net has been changed to include MySqlDataReader.GetFieldType(string columnname). Further, MySqlDataReader.GetOrdinal() now includes the name of the column in the exception if the column is not found. (Bug #47467)

A non-terminated string in SQL threw a CLR exception rather than a syntax exception. (Bug #51788)

When calling ExecuteNonQuery on a command object, the following exception occurred:

Index and length must refer to a location within the string.
Parameter name: length

(Bug #51610)

Specifying a connection string where an option had no value generated an error, rather than the value being set to the default. For example, a connection string such as the following would result in an error:

server=localhost;user=root;compress=;database=test;port=3306;password=123456;

(Bug #51209)

The method Command.TrimSemicolons used StringBuilder, and therefore allocated memory for the query even if it did not need to be trimmed. This led to excessive memory consumption when executing a number of large queries. (Bug #51149)

MySqlCommand.Parameters.Clear() did not work. (Bug #50444)

When the MySqlScript.execute() method was called, the following exception was generated:

InvalidOperationException : The CommandText property has not been properly initialized.

(Bug #50344)

When using the Compact Framework the following exception occurred when attempting to connect to a MySQL Server:

System.InvalidOperationException was unhandled
  Message="Timeouts are not supported on this stream."

(Bug #50321)

Binary Columns were not displayed in the Query Builder of Visual Studio. (Bug #50171)

When the UpdateBatchSize property was set to a value greater than 1, only the first row was applied to the database. (Bug #50123)

When using table per type inheritance and listing the contents of the parent table, the result of the query was a list of child objects, even though there was no related child record with the same parent Id. (Bug #49850)

MySqlDataReader.GetUInt64 returned an incorrect value when reading a BIGINT UNSIGNED column containing a value greater than 2147483647. (Bug #49794)

A FormatException was generated when an empty string was returned from a stored function. (Bug #49642)

When trying to create stored procedures from an SQL script, a MySqlException was thrown when attempting to redefine the DELIMITER:

MySql.Data.MySqlClient.MySqlException was unhandled
Message="You have an error in your SQL syntax; check the manual that corresponds to your
MySQL server version for the right syntax to use near 'DELIMITER' at line 1"
Source="MySql.Data"
ErrorCode=-2147467259
Number=1064
StackTrace:
à MySql.Data.MySqlClient.MySqlStream.ReadPacket()
à MySql.Data.MySqlClient.NativeDriver.ReadResult(UInt64& affectedRows, Int64&
lastInsertId)
à MySql.Data.MySqlClient.MySqlDataReader.GetResultSet()
à MySql.Data.MySqlClient.MySqlDataReader.NextResult()
à MySql.Data.MySqlClient.MySqlCommand.ExecuteReader(CommandBehavior behavior)
à MySql.Data.MySqlClient.MySqlCommand.ExecuteReader()
à MySql.Data.MySqlClient.MySqlCommand.ExecuteNonQuery()
à MySql.Data.MySqlClient.MySqlScript.Execute()

Note: The MySqlScript class has been fixed to support the delimiter statement as it is found in SQL scripts. (Bug #46429)

Calling a User Defined Function using Entity SQL in the Entity Framework caused a NullReferenceException. (Bug #45277)

A connection string set in web.config could not be reused after Visual Studio 2008 Professional was shut down. It continued working for the existing controls, but did not work for new controls added. (Bug #41629)

When adding a data set in Visual Studio 2008, the following error was generated:

Relations couldn't be added. Column 'REFERENCED_TABLE_CATALOG' does not belong to table.

This was due to a 'REFERENCED_TABLE_CATALOG' column not being included in the foreign keys collection. (Bug #48974)

Attempting to execute a load data local infile on a file where the user did not have write permissions, or the file was open in an editor gave an access denied error. (Bug #48944)

The method MySqlDataReader.GetSchemaTable() returned 0 in the NumericPrecision field for decimal and newdecimal columns. (Bug #48171)

MySQL Connector/Net generated an invalid operation exception during a transaction rollback:

System.InvalidOperationException: Connection must be valid and open to rollback
transaction
   at MySql.Data.MySqlClient.MySqlTransaction.Rollback()
   at MySql.Data.MySqlClient.MySqlConnection.CloseFully()
   at
MySql.Data.MySqlClient.MySqlPromotableTransaction.System.Transactions.IPromotableSinglePhaseNotification.Rollback(SinglePhaseEnlistment
singlePhaseEnlistment)
...

(Bug #35330)

Connection objects were not garbage collected when not in use. (Bug #31996)

Functionality Added or Changed

Bugs Fixed

The MySqlParameter class now has a property named PossibleValues. This property is NULL unless the parameter is created by MySqlCommandBuilder.DeriveParameters. Further, it will be NULL unless the parameter is of type enum or set - in this case it will be a list of strings that are the possible values for the column. This feature is designed as an aid to the developer. (Bug #48586)

Prior to MySQL Connector/Net 6.2, MySqlCommand.CommandTimeout included user processing time, that is processing time not related to direct use of the connector. Timeout was implemented through a .NET Timer, that triggered after CommandTimeout seconds.

MySQL Connector/Net 6.2 introduced timeouts that are aligned with how Microsoft handles SqlCommand.CommandTimeout. This property is the cumulative timeout for all network reads and writes during command execution or processing of the results. A timeout can still occur in the MySqlReader.Read method after the first row is returned, and does not include user processing time, only IO operations.

Further details on this can be found in the relevant Microsoft documentation.

Starting with MySQL Connector/Net 6.2, there is a background job that runs every three minutes and removes connections from pool that have been idle (unused) for more than three minutes. The pool cleanup frees resources on both client and server side. This is because on the client side every connection uses a socket, and on the server side every connection uses a socket and a thread.

Prior to this change, connections were never removed from the pool, and the pool always contained the peak number of open connections. For example, a web application that peaked at 1000 concurrent database connections would consume 1000 threads and 1000 open sockets at the server, without ever freeing up those resources from the connection pool.

MySQL Connector/Net now supports the processing of certificates when connecting to an SSL-enabled MySQL Server. For further information see the connection string option SSL Mode in the section Connector/Net Connection String Options Reference and the tutorial Tutorial: Using SSL with MySQL Connector/Net.

Cloning of MySqlCommand was not typesafe. To clone a MySqlCommand it was necessary to do:

MySqlCommand clone = (MySqlCommand)((ICloneable)comm).Clone();

MySQL Connector/Net was changed so that it was possible to do:

MySqlCommand clone = comm.Clone();

(Bug #48460)

When used, the Encrypt connection string option caused a “Keyword not supported” exception to be generated.

This option is in fact obsolete, and the option SSL Mode should be used instead. Although the Encrypt option has been fixed so that it does not generate an exception, it will be removed completely in version 6.4. (Bug #48290)

When building the MySql.Data project with .NET Framework 3.5 installed, the following build output was displayed:

Project file contains ToolsVersion="4.0", which is not supported by this version of
MSBuild. Treating the project as if it had ToolsVersion="3.5".

The project had been created using the .NET Framework 4.0, which was beta, instead of using the 3.5 framework. (Bug #48271)

It was not possible to retrieve a value from a MySQL server table, if the value was larger than that supported by the .NET type System.Decimal.

MySQL Connector/Net was changed to expose the MySqlDecimal type, along with the supporting method GetMySqlDecimal. (Bug #48100)

An entity model created from a schema containing a table with a column of type UNSIGNED BIGINT and a view of the table did not behave correctly. When an entity was created and mapped to the view, the column that was of type UNSIGNED BIGINT was displayed as BIGINT. (Bug #47872)

MySQL Connector/Net session support did not work with MySQL Server versions prior to 5.0, as the Session Provider used a call to TIMESTAMPDIFF, which was not available on servers prior to 5.0. (Bug #47219)

When using a BINARY(16) column to represent a GUID and having specified “old guids = true” in the connection string, the values were returned correctly until a null value was encountered in that field. After the null value was encountered a format exception was thrown with the following message:

Guid should contain 32 digits with 4 dashes (xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx).

(Bug #47928)

The Session Provider created invalid “session expires” on a random basis.

This was due to the fact that the Session Provider was incorrectly reading from the root web.config, rather than from the application specific web.config. (Bug #47815)

When loading the MySQLClient-mono.sln file included with the Connector/Net source into Mono Develop, the following error occurred:

/home/tbedford/connector-net-src/6.1/MySQLClient-mono.sln(22):
Unsupported or unrecognized project:
'/home/tbedford/connector-net-src/6.1/Installer/Installer.wixproj'

If the file was modified to remove this problem, then attempting to build the solution generated the following error:

/home/tbedford/connector-net-src/6.1/MySql.Data/Provider/Source/Connection.cs(280,46):
error CS0115: `MySql.Data.MySqlClient.MySqlConnection.DbProviderFactory' is marked as an
override but no suitable property found to override

(Bug #47048)

MySqlScript was modified to enable correct processing of the DELIMITER command when not followed by a new line. (Bug #61680, Bug #12732279)

SchemaDefinition-5.5.ssdl was modified to treat CHAR(36) columns as a GUID. (Bug #61657, Bug #12708208)

SqlFragment.QuoteIdentifier was modified to add MySQL quotes around identifiers. (Bug #61635, Bug #12707285)

The ASP.NET membership provider was modified to create and query all related tables using lowercase names. (Bug #61108, Bug #12702009)

MySQLConnectionStringBuilder.ContainsKey() incorrectly returned false when testing whether a keyword was part of the connection string. (Bug #11766671, Bug #59835)

Modified MySqlConnection.BeginTransaction to throw a NotSupportedException for Snapshot isolation level. (Bug #61589, Bug #12698020)

MysqlDataReader.GetSchemaTable returned incorrect values and types. (Bug #59989, Bug #11776346)

All queries other than INSERT were executed individually instead of as a batch even though batching was enabled for the connection. (Bug #59616, Bug #11850286)

MySQL Connector/Net generated an exception when executing a query consisting of ';', for example:

mycmd(";",mycon)
mycmd.executenonquery()

The exception generated was:

System.IndexOutOfRangeException: Index was outside the bounds of the array.
   at MySql.Data.MySqlClient.MySqlCommand.TrimSemicolons(String sql)
   at MySql.Data.MySqlClient.MySqlCommand.ExecuteReader(CommandBehavior behavior)
   at MySql.Data.MySqlClient.MySqlCommand.ExecuteReader()
   at MySql.Data.MySqlClient.MySqlCommand.ExecuteNonQuery()

(Bug #59537, Bug #11766433)

Setting Membership.ApplicationName had no effect. (Bug #59438, Bug #11770465)

MembershipProvider did not generate hashes correctly if the algorithm was keyed. The Key of the algorithm should have been set if the HashAlgorithm was KeyedHashAlgorithm. (Bug #58906)

Code introduced to fix bug #54863 proved problematic on .NET version 3.5 and above. (Bug #58853)

The MySqlTokenizer contained unnecessary Substring and Trim calls:

string token = sql.Substring(startIndex, stopIndex - startIndex).Trim();

The variable token was not used anywhere in the code. (Bug #58757)

MySqlCommand.ExecuteReader(CommandBehavior) threw a NullReferenceException when being called with CommandBehavior.CloseConnection, if the SQL statement contained a syntax error, or contained invalid data such as an invalid column name. (Bug #58652)

ReadFieldLength() returned incorrect value for BIGINT autoincrement columns. (Bug #58373)

MySQL Connector/Net did not support the utf8mb4 character set. When attempting to connect to utf8mb4 tables or columns, an exception KeyNotFoundException was generated. (Bug #58244)

A typed dataset did not get the table name. (Bug #57894, Bug #11764989)

Setting MySqlCommand.CommandTimeout to 0 had no effect. It should have resulted in an infinite timeout. (Bug #57265)

When performing a row-by-row update, only the first row was updated and all other rows were ignored. (Bug #57092)

Setting the Default Command Timeout connection string option had no effect. (Bug #56806)

When an output parameter was declared as type MySqlDbType.Bit, it failed to return with the correct value. (Bug #56756)

MySqlHelper.ExecuteReader did not include an overload accepting MySqlParameter objects when using a MySqlConnection. However, MySqlHelper did include an overload for MySqlParameter objects when using a string object containing the connection string to the database. (Bug #56755)

Default values returned for text columns were not quoted. This meant that the COLUMN_DEFAULT field of the GetSchema columns collection did not return a valid SQL expression. (Bug #56509)

MySQL Connector/Net for .NET/Mono attempted to dynamically load the assembly Mono.Posix.dll when a Unix socket was used to connect to the server. This failed and the connector was not able to use a Unix socket unless the Mono.Posix.dll assembly was previously loaded by the program. (Bug #56410)

Modified ProviderManifest.xml to map TIMESTAMP database columns to the DateTime .NET type. (Bug #55351, Bug #12652602)

The ADO.NET Entity Data Model could not add stored procedures from MySQL Server 5.0.45 but worked fine using MySQL Server 5.1. (Bug #55349)

Fixed Entity Framework provider GROUP BY clause generation by adding all group-by keys to the SELECT statement. (Bug #46742, Bug #12622129)

The calculation of lockAge in the Session Provider sometimes generated a System.Data.SqlTypes.SqlNullValueException. (Bug #55701)

Attempting to read Double.MinValue from a DOUBLE column in MySQL table generated the following exception:

System.OverflowException : Value was either too large or too small for a Double.

--OverflowException
at System.Number.ParseDouble(String value, NumberStyles options, NumberFormatInfo
numfmt)
at MySql.Data.Types.MySqlDouble.MySql.Data.Types.IMySqlValue.ReadValue(MySqlPacket
packet, Int64 length, Boolean nullVal)
at MySql.Data.MySqlClient.NativeDriver.ReadColumnValue(Int32 index, MySqlField field,
IMySqlValue valObject)
at MySql.Data.MySqlClient.ResultSet.ReadColumnData(Boolean outputParms)
at MySql.Data.MySqlClient.ResultSet.NextRow(CommandBehavior behavior)
at MySql.Data.MySqlClient.MySqlDataReader.Read()

(Bug #55644)

If using MySQL Server 5.0.x it was not possible to alter stored routines in Visual Studio. If the stored routine was clicked, and the context sensitive menu option, Alter Routine, selected, the following error was generated:

Unable to load object with error: Object reference not
set to an instance of an object

(Bug #55170)

MySqlDataAdapter.Update() generated concurrency violations for custom stored procedure driven update commands that used UpdateRowSource.FirstReturnedRecord. (Bug #54895)

Several calls to DataAdapter.Update() with intervening changes to DataTable resulted in ConcurrencyException exceptions being generated. (Bug #54863)

The icon for the MySQL Web Configuration Tool was not displayed in Visual Studio for Web Application Projects. (Bug #54571)

The MySqlHelper object did not have an overloaded version of the ExecuteReader method that accepted a MySqlConnection object. (Bug #54570)

If MySqlDataAdapter was used with an INSERT command where the VALUES clause contained an expression with parentheses in it, and set the adapter.UpdateBatchSize parameter to be greater than one, then the call to adapter.Update either generated an exception or failed to batch the commands, executing each insert individually. (Bug #54386)

The method MySql.Data.Common.QueryNormalizer.CollapseValueList generated an ArgumentOutOfRangeException. (Bug #54152, Bug #53865)

Garbage Collector disposal of a MySqlConnection object caused the following exception:

System.IO.EndOfStreamException: Attempted to read past the end of the stream.
MySql.Data.MySqlClient.MySqlStream.ReadFully(Stream stream, Byte[] buffer, Int32 offset,
Int32 count)
MySql.Data.MySqlClient.MySqlStream.LoadPacket()
Outer Exception Reading from the stream has failed.
...

(Bug #53457)

MySQL Connector/Net did not throw an EndOfStreamException exception when net_write_timeout was exceeded. (Bug #53439)

After a timeout exception, if an attempt was made to reuse a connection returned to the connection pool the following exception was generated:

[MySqlException (0x80004005): There is already an open DataReader associated with this
Connection which must be closed first.]
   MySql.Data.MySqlClient.MySqlCommand.CheckState() +278
   MySql.Data.MySqlClient.MySqlCommand.ExecuteReader(CommandBehavior behavior) +43
   MySql.Data.MySqlClient.MySqlCommand.ExecuteReader() +6
   Controls.SimpleCommand.ExecuteReader(String SQL) in ...:323
   Albums.GetImagesByAlbum(SimpleCommand Cmd, Int32 iAlbum, String Order, String Limit)
in ...:13
   Forecast.Page_Load(Object sender, EventArgs e) in ...:70
   System.Web.UI.Control.OnLoad(EventArgs e) +99
   System.Web.UI.Control.LoadRecursive() +50
   System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean
includeStagesAfterAsyncPoint) +627

(Bug #53357)

Membership schema creation failed if the default schema collation was not Latin1. (Bug #53174)

EventLog was not disposed in the SessionState provider. (Bug #52550)

CHAR(36) columns were not recognized as GUIDs when used in views with entity models. (Bug #52085)

Stored procedure enumeration code generated an error if a procedure was used in a dataset that did not return any resultsets. (Bug #50671)

When an application was subjected to increased concurrent load, MySQL Connector/Net generated the following error when calling stored procedures:

A DataTable named \'Procedure Parameters\'
already belongs to this DataSet.

(Bug #49118)

In the ADO.NET Entity Data Model Wizard, the time to update a model scaled abnormally as the number of entities increased. (Bug #48791, Bug #12596237)

The INSERT command was significantly slower with MySQL Connector/Net 6.x compared to 5.x, when compression was enabled. (Bug #48243)

When the connection string option “Connection Reset = True” was used, a connection reset used the previously used encoding for the subsequent authentication operation. This failed, for example, if UCS2 was used to read the last column before the reset. (Bug #47153)

Opening a connection in the Visual Studio Server Explorer and choosing to alter an existing routine required another authentication at the server. (Bug #44715)

When batching was used in MySqlDataAdapter, a connection was not opened automatically in MySqlDataAdapter.Update(). This resulted in an InvalidOperationException exception being generated, with the message text “connection must be valid and open”.

MySQL Connector/Net has been changed to behave more like SQL Server: if the connection is closed, it is opened for the duration of update operation. (Bug #38411)

Database name was emitted into typed datasets. This prevented users using the configured default database. (Bug #33870)

Functionality Added or Changed

Bugs Fixed

Procedure caching had a problem whereby if you created a procedure, dropped it, and recreated it with a different number of parameters an exception was generated.

MySQL Connector/Net has been changed so that if the procedure is recreated with a different number of parameters, it will still be recognized. (Bug #52562)

MySQL Connector/Net has been changed to include MySqlDataReader.GetFieldType(string columnname). Further, MySqlDataReader.GetOrdinal() now includes the name of the column in the exception if the column is not found. (Bug #47467)

In MySQL Connector/Net, the MySqlConnection.Abort() method contained a try...catch construct, with an empty catch block. This meant that any exception generated at this point would not be caught. (Bug #52769)

If FunctionsReturnString=true was used in the connection string, the decimal separator (according to locale) was not interpreted. (Bug #52187)

In MySQL Connector/Net, the LoadCharsetMap() function of the CharSetMap class set the following incorrect mapping:

mapping.Add("latin1", new CharacterSet("latin1", 1));

This meant that, for example, the Euro sign was not handled correctly.

The correct mapping should have been:

mapping.Add("latin1", new CharacterSet("windows-1252", 1));

This is because the MySQL latin1 character set is the same as the windows-cp1252 character set and it extends the official ISO 8859-1 or IANA latin1. (Bug #51927)

A non-terminated string in SQL threw a CLR exception rather than a syntax exception. (Bug #51788)

When calling ExecuteNonQuery on a command object, the following exception occurred:

Index and length must refer to a location within the string.
Parameter name: length

(Bug #51610)

The method Command.TrimSemicolons used StringBuilder, and therefore allocated memory for the query even if it did not need to be trimmed. This led to excessive memory consumption when executing a number of large queries. (Bug #51149)

MySqlCommand.Parameters.Clear() did not work. (Bug #50444)

When the MySqlScript.execute() method was called, the following exception was generated:

InvalidOperationException : The CommandText property has not been properly initialized.

(Bug #50344)

Binary Columns were not displayed in the Query Builder of Visual Studio. (Bug #50171)

When the UpdateBatchSize property was set to a value greater than 1, only the first row was applied to the database. (Bug #50123)

When using table per type inheritance and listing the contents of the parent table, the result of the query was a list of child objects, even though there was no related child record with the same parent Id. (Bug #49850)

MySqlDataReader.GetUInt64 returned an incorrect value when reading a BIGINT UNSIGNED column containing a value greater than 2147483647. (Bug #49794)

A FormatException was generated when an empty string was returned from a stored function. (Bug #49642)

When adding a data set in Visual Studio 2008, the following error was generated:

Relations couldn't be added. Column 'REFERENCED_TABLE_CATALOG' does not belong to table.

This was due to a 'REFERENCED_TABLE_CATALOG' column not being included in the foreign keys collection. (Bug #48974)

Attempting to execute a load data local infile on a file where the user did not have write permissions, or the file was open in an editor gave an access denied error. (Bug #48944)

The method MySqlDataReader.GetSchemaTable() returned 0 in the NumericPrecision field for decimal and newdecimal columns. (Bug #48171)

When trying to create stored procedures from an SQL script, a MySqlException was thrown when attempting to redefine the DELIMITER:

MySql.Data.MySqlClient.MySqlException was unhandled
Message="You have an error in your SQL syntax; check the manual that corresponds to your
MySQL server version for the right syntax to use near 'DELIMITER' at line 1"
Source="MySql.Data"
ErrorCode=-2147467259
Number=1064
StackTrace:
à MySql.Data.MySqlClient.MySqlStream.ReadPacket()
à MySql.Data.MySqlClient.NativeDriver.ReadResult(UInt64& affectedRows, Int64&
lastInsertId)
à MySql.Data.MySqlClient.MySqlDataReader.GetResultSet()
à MySql.Data.MySqlClient.MySqlDataReader.NextResult()
à MySql.Data.MySqlClient.MySqlCommand.ExecuteReader(CommandBehavior behavior)
à MySql.Data.MySqlClient.MySqlCommand.ExecuteReader()
à MySql.Data.MySqlClient.MySqlCommand.ExecuteNonQuery()
à MySql.Data.MySqlClient.MySqlScript.Execute()

Note: The MySqlScript class has been fixed to support the delimiter statement as it is found in SQL scripts. (Bug #46429)

Calling a User Defined Function using Entity SQL in the Entity Framework caused a NullReferenceException. (Bug #45277)

A connection string set in web.config could not be reused after Visual Studio 2008 Professional was shut down. It continued working for the existing controls, but did not work for new controls added. (Bug #41629)

Cloning of MySqlCommand was not typesafe. To clone a MySqlCommand it was necessary to do:

MySqlCommand clone = (MySqlCommand)((ICloneable)comm).Clone();

MySQL Connector/Net was changed so that it was possible to do:

MySqlCommand clone = comm.Clone();

(Bug #48460)

When building the MySql.Data project with .NET Framework 3.5 installed, the following build output was displayed:

Project file contains ToolsVersion="4.0", which is not supported by this version of
MSBuild. Treating the project as if it had ToolsVersion="3.5".

The project had been created using the .NET Framework 4.0, which was beta, instead of using the 3.5 framework. (Bug #48271)

If MySqlConnection.GetSchema was called for "Indexes" on a table named “b`a`d” as follows:

DataTable schemaPrimaryKeys = connection.GetSchema(
  "Indexes",
  new string[] { null, schemaName, "b`a`d"});

Then the following exception was generated:

You have an error in your SQL syntax; check the manual that corresponds to
your MySQL server version for the right syntax to use near 'a`d`' at line 1

(Bug #48101)

It was not possible to retrieve a value from a MySQL server table, if the value was larger than that supported by the .NET type System.Decimal.

MySQL Connector/Net was changed to expose the MySqlDecimal type, along with the supporting method GetMySqlDecimal. (Bug #48100)

For some character sets such as UTF-8, a CHAR column would sometimes be incorrectly interpreted as a GUID by MySQL Connector/Net.

MySQL Connector/Net was changed so that a column would only be interpreted as a GUID if it had a character length of 36, as opposed to a byte length of 36. (Bug #47985)

When using a BINARY(16) column to represent a GUID and having specified “old guids = true” in the connection string, the values were returned correctly until a null value was encountered in that field. After the null value was encountered a format exception was thrown with the following message:

Guid should contain 32 digits with 4 dashes (xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx).

(Bug #47928)

An entity model created from a schema containing a table with a column of type UNSIGNED BIGINT and a view of the table did not behave correctly. When an entity was created and mapped to the view, the column that was of type UNSIGNED BIGINT was displayed as BIGINT. (Bug #47872)

The Session Provider created invalid “session expires” on a random basis.

This was due to the fact that the Session Provider was incorrectly reading from the root web.config, rather than from the application specific web.config. (Bug #47815)

Attempting to build MySQL Connector/Net 6.1 MySQL.Data from source code on Windows failed with the following error:

...\clones\6.1\MySql.Data\Provider\Source\NativeDriver.cs(519,29): error CS0122:
'MySql.Data.MySqlClient.MySqlPacket.MySqlPacket()' is inaccessible due to its protection level

(Bug #47354)

When tables were auto created for the Session State Provider they were set to use the MySQL Server's default collation, rather than the default collation set for the containing database. (Bug #47332)

When loading the MySQLClient-mono.sln file included with the Connector/Net source into Mono Develop, the following error occurred:

/home/tbedford/connector-net-src/6.1/MySQLClient-mono.sln(22):
Unsupported or unrecognized project:
'/home/tbedford/connector-net-src/6.1/Installer/Installer.wixproj'

If the file was modified to remove this problem, then attempting to build the solution generated the following error:

/home/tbedford/connector-net-src/6.1/MySql.Data/Provider/Source/Connection.cs(280,46):
error CS0115: `MySql.Data.MySqlClient.MySqlConnection.DbProviderFactory' is marked as an
override but no suitable property found to override

(Bug #47048)

The MySQL Connector/Net Session State Provider truncated session data to 64KB, due to its column types being set to BLOB. (Bug #47339)

MySQL Connector/Net generated the following exception when using the Session State provider:

You have an error in your SQL syntax; check the manual that corresponds to your MySQL
server version for the right syntax to use near 'MINUTEWHERE SessionId =
'dtmgga55x35oi255nrfrxe45' AND ApplicationId = 1 AND Loc' at line 1
Description: An unhandled exception occurred during the execution of the current web
request. Please review the stack trace for more information about the error and where it
originated in the code.

Exception Details: MySql.Data.MySqlClient.MySqlException: You have an error in your SQL
syntax; check the manual that corresponds to your MySQL server version for the right
syntax to use near 'MINUTEWHERE SessionId = 'dtmgga55x35oi255nrfrxe45' AND ApplicationId =
1 AND Loc' at line 1

(Bug #46939)

If an error occurred during connection to a MySQL Server, deserializing the error message from the packet buffer caused a NullReferenceException to be thrown. When the method MySqlPacket::ReadString() attempted to retrieve the error message, the following line of code threw the exception:

string s = encoding.GetString(bits, (int)buffer.Position, end - (int)buffer.Position);

This was due to the fact that the encoding field had not been initialized correctly. (Bug #46844)

Input parameters were missing from Stored Procedures when using them with ADO.NET Data Entities. (Bug #44985)

MySQL Connector/Net did not time out correctly. The command timeout was set to 30 secs, but MySQL Connector/Net hung for several hours. (Bug #43761)

In the MySqlDataReader class the GetSByte function returned a byte value instead of an sbyte value. (Bug #46620)

The MySQL Connector/Net Profile Provider, MySql.Web.Profile.MySQLProfileProvider, generated an error when running on Mono. When an attempt was made to save a string in Profile.Name the string was not saved to the my_aspnet_Profiles table. If an attempt was made to force the save with Profile.Save() the following error was generated:

Server Error in '/mono' Application

--------------------------------------------------------------------------------

The requested feature is not implemented.
Description: HTTP 500. Error processing request.

Stack Trace:

System.NotImplementedException: The requested feature is not implemented.
at MySql.Data.MySqlClient.MySqlConnection.EnlistTransaction
(System.Transactions.Transaction transaction) [0x00000]
at MySql.Data.MySqlClient.MySqlConnection.Open () [0x00000]
at MySql.Web.Profile.MySQLProfileProvider.SetPropertyValues
(System.Configuration.SettingsContext context,
System.Configuration.SettingsPropertyValueCollection collection) [0x00000]


--------------------------------------------------------------------------------
Version information: Mono Version: 2.0.50727.1433; ASP.NET Version: 2.0.50727.1433

(Bug #46375)

An exception was generated when using TIMESTAMP columns with the Entity Framework. (Bug #46311)

MySQL Connector/Net sometimes hung, without generating an exception. This happened if a read from a stream failed returning a 0, causing the code in LoadPacket() to enter an infinite loop. (Bug #46308)

When using MySQL Connector/Net 6.0.4 and a MySQL Server 4.1 an exception was generated when trying to execute:

connection.GetSchema("Columns", ...);

The exception generated was:

'connection.GetSchema("Columns")' threw an exception of type
'System.ArgumentException'System.Data.DataTable {System.ArgumentException}
base{"Input string was not in a correct format.Couldn't store <'Select'> in
NUMERIC_PRECISION Column.  Expected type is UInt64."}System.Exception
{System.ArgumentException}

(Bug #46270)

The MySQL Connector/Net method StoredProcedure.GetParameters(string) ignored the programmer's setting of the UseProcedureBodies option. This broke any application for which the application's parameter names did not match the parameter names in the Stored Procedure, resulting in an ArgumentException with the message “Parameter 'foo' not found in the collection.” and the following stack trace:

MySql.Data.dll!MySql.Data.MySqlClient.MySqlParameterCollection.GetParameterFlexible(stri
ng parameterName = "pStart", bool throwOnNotFound = true) Line 459C#
MySql.Data.dll!MySql.Data.MySqlClient.StoredProcedure.Resolve() Line 157 + 0x25
bytesC#
MySql.Data.dll!MySql.Data.MySqlClient.MySqlCommand.ExecuteReader(System.Data.CommandBeha
vior behavior = SequentialAccess) Line 405 + 0xb bytesC#
MySql.Data.dll!MySql.Data.MySqlClient.MySqlCommand.ExecuteDbDataReader(System.Data.Comma
ndBehavior behavior = SequentialAccess) Line 884 + 0xb bytesC#
System.Data.dll!System.Data.Common.DbCommand.System.Data.IDbCommand.ExecuteReader(System
.Data.CommandBehavior behavior) + 0xb bytes
System.Data.dll!System.Data.Common.DbDataAdapter.FillInternal(System.Data.DataSet
dataset = {System.Data.DataSet}, System.Data.DataTable[] datatables = null, int
startRecord = 0, int maxRecords = 0, string srcTable = "Table", System.Data.IDbCommand
command = {MySql.Data.MySqlClient.MySqlCommand}, System.Data.CommandBehavior behavior) +
0x83 bytes
System.Data.dll!System.Data.Common.DbDataAdapter.Fill(System.Data.DataSet dataSet, int
startRecord, int maxRecords, string srcTable, System.Data.IDbCommand command,
System.Data.CommandBehavior behavior) + 0x120 bytes
System.Data.dll!System.Data.Common.DbDataAdapter.Fill(System.Data.DataSet dataSet) +
0x5f bytes

(Bug #46213)

Conversion of MySQL TINYINT(1) to boolean failed. (Bug #46205, Bug #46359, Bug #41953)

When populating a MySQL database table in Visual Studio using the Table Editor, if a VARCHAR(10) column was changed to a VARCHAR(20) column an exception was generated:

SystemArgumentException: DataGridViewComboBoxCell value is not valid.
To replace this default dialog please handle the DataError Event.

(Bug #46100)

The Entity Framework provider was not calling DBSortExpression correctly when the Skip and Take methods were used, such as in the following statement:

TestModel.tblquarantine.OrderByDescending(q => q.MsgDate).Skip(100).Take(100).ToList();

This resulted in the data being unsorted. (Bug #45723)

The MySQL Connector/Net 6.0.4 installer failed with an error. The error message generated was:

There is a problem with this Windows Installer package. A DLL required for this
install to complete could not be run. Contact your support personnel or package vendor.

When OK was clicked to acknowledge the error the installer exited. (Bug #45474)

Calling the Entity Framework SaveChanges() method of any MySQL ORM Entity with a column type TIME, generated an error message:

Unknown PrimitiveKind Time

(Bug #45457)

Insert into two tables failed when using the Entity Framework. The exception generated was:

The value given is not an instance of type 'Edm.Int32'

(Bug #45077)

Errors occurred when using the Entity Framework with cultures that used a comma as the decimal separator. This was because the formatting for SINGLE, DOUBLE and DECIMAL values was not handled correctly. (Bug #44455)

When attempting to connect to MySQL using the Compact Framework version of MySQL Connector/Net, an IndexOutOfRangeException exception was generated on trying to open the connection. (Bug #43736)

When reading data, such as with a MySqlDataAdapter on a MySqlConnection, MySQL Connector/Net could potentially enter an infinite loop in CompressedStream.ReadNextpacket() if compression was enabled. (Bug #43678)

An error occurred when building MySQL Connector/Net from source code checked out from the public SVN repository. This happened on Linux using Mono and Nant. The Mono JIT compiler version was 1.2.6.0. The Nant version was 0.85.

When an attempt was made to build (for example) the MySQL Connector/Net 5.2 branch using the command:

$ nant -buildfile:Client.build

The following error occurred:

BUILD FAILED

Error loading buildfile.
Encoding name 'Windows-1252' not supported.
Parameter name: name

(Bug #42411)

MySQL Connector/Net CHM documentation stated that MySQL Server 3.23 was supported. (Bug #42110)

In the case of long network inactivity, especially when connection pooling was used, connections were sometimes dropped, for example, by firewalls.

Note: The bugfix introduced a new keepalive parameter, which prevents disconnects by sending an empty TCP packet after a specified timeout. (Bug #40684)

Calling a Stored Procedure with an output parameter through MySQL Connector/Net resulted in a memory leak. Calling the same Stored Procedure without an output parameter did not result in a memory leak. (Bug #36027)

Changed GUID type - The backend representation of a guid type has been changed to be CHAR(36). This is so you can use the server UUID() function to populate a GUID table. UUID generates a 36 character string. Developers of older applications can add old guids=true to the connection string and the old BINARY(16) type will be used instead.

Support for native output parameters - This is supported when connected to a server that supports native output parameters. This includes servers as of 5.5.3 and 6.0.8.

Session State Provider - This enables you to store the state of your website in a MySQL server.

Website Configuration Dialog - This is a new wizard that is activated by clicking a button on the toolbar at the top of the Visual Studio Solution Explorer. It works in conjunction with the ASP.Net administration pages, making it easier to activate and set advanced options for the different MySQL web providers included.

MySQLConnectionStringBuilder.ContainsKey() incorrectly returned false when testing whether a keyword was part of the connection string. (Bug #11766671, Bug #59835)

MysqlDataReader.GetSchemaTable returned incorrect values and types. (Bug #59989, Bug #11776346)

All queries other than INSERT were executed individually instead of as a batch even though batching was enabled for the connection. (Bug #59616, Bug #11850286)

MySQL Connector/Net generated an exception when executing a query consisting of ';', for example:

mycmd(";",mycon)
mycmd.executenonquery()

The exception generated was:

System.IndexOutOfRangeException: Index was outside the bounds of the array.
   at MySql.Data.MySqlClient.MySqlCommand.TrimSemicolons(String sql)
   at MySql.Data.MySqlClient.MySqlCommand.ExecuteReader(CommandBehavior behavior)
   at MySql.Data.MySqlClient.MySqlCommand.ExecuteReader()
   at MySql.Data.MySqlClient.MySqlCommand.ExecuteNonQuery()

(Bug #59537, Bug #11766433)

Setting Membership.ApplicationName had no effect. (Bug #59438, Bug #11770465)

MembershipProvider did not generate hashes correctly if the algorithm was keyed. The Key of the algorithm should have been set if the HashAlgorithm was KeyedHashAlgorithm. (Bug #58906)

Code introduced to fix bug #54863 proved problematic on .NET version 3.5 and above. (Bug #58853)

The MySqlTokenizer contained unnecessary Substring and Trim calls:

string token = sql.Substring(startIndex, stopIndex - startIndex).Trim();

The variable token was not used anywhere in the code. (Bug #58757)

MySqlCommand.ExecuteReader(CommandBehavior) threw a NullReferenceException when being called with CommandBehavior.CloseConnection, if the SQL statement contained a syntax error, or contained invalid data such as an invalid column name. (Bug #58652)

ReadFieldLength() returned incorrect value for BIGINT autoincrement columns. (Bug #58373)

MySQL Connector/Net did not support the utf8mb4 character set. When attempting to connect to utf8mb4 tables or columns, an exception KeyNotFoundException was generated. (Bug #58244)

A typed dataset did not get the table name. (Bug #57894, Bug #11764989)

Setting MySqlCommand.CommandTimeout to 0 had no effect. It should have resulted in an infinite timeout. (Bug #57265)

When performing a row-by-row update, only the first row was updated and all other rows were ignored. (Bug #57092)

Setting the Default Command Timeout connection string option had no effect. (Bug #56806)

When an output parameter was declared as type MySqlDbType.Bit, it failed to return with the correct value. (Bug #56756)

Default values returned for text columns were not quoted. This meant that the COLUMN_DEFAULT field of the GetSchema columns collection did not return a valid SQL expression. (Bug #56509)

MySQL Connector/Net for .NET/Mono attempted to dynamically load the assembly Mono.Posix.dll when a Unix socket was used to connect to the server. This failed and the connector was not able to use a Unix socket unless the Mono.Posix.dll assembly was previously loaded by the program. (Bug #56410)

The ADO.NET Entity Data Model could not add stored procedures from MySQL Server 5.0.45 but worked fine using MySQL Server 5.1. (Bug #55349)

Attempting to read Double.MinValue from a DOUBLE column in MySQL table generated the following exception:

System.OverflowException : Value was either too large or too small for a Double.

--OverflowException
at System.Number.ParseDouble(String value, NumberStyles options, NumberFormatInfo
numfmt)
at MySql.Data.Types.MySqlDouble.MySql.Data.Types.IMySqlValue.ReadValue(MySqlPacket
packet, Int64 length, Boolean nullVal)
at MySql.Data.MySqlClient.NativeDriver.ReadColumnValue(Int32 index, MySqlField field,
IMySqlValue valObject)
at MySql.Data.MySqlClient.ResultSet.ReadColumnData(Boolean outputParms)
at MySql.Data.MySqlClient.ResultSet.NextRow(CommandBehavior behavior)
at MySql.Data.MySqlClient.MySqlDataReader.Read()

(Bug #55644)

MySqlDataAdapter.Update() generated concurrency violations for custom stored procedure driven update commands that used UpdateRowSource.FirstReturnedRecord. (Bug #54895)

Several calls to DataAdapter.Update() with intervening changes to DataTable resulted in ConcurrencyException exceptions being generated. (Bug #54863)

The MySqlHelper object did not have an overloaded version of the ExecuteReader method that accepted a MySqlConnection object. (Bug #54570)

If MySqlDataAdapter was used with an INSERT command where the VALUES clause contained an expression with parentheses in it, and set the adapter.UpdateBatchSize parameter to be greater than one, then the call to adapter.Update either generated an exception or failed to batch the commands, executing each insert individually. (Bug #54386)

The method MySql.Data.Common.QueryNormalizer.CollapseValueList generated an ArgumentOutOfRangeException. (Bug #54152, Bug #53865)

Garbage Collector disposal of a MySqlConnection object caused the following exception:

System.IO.EndOfStreamException: Attempted to read past the end of the stream.
MySql.Data.MySqlClient.MySqlStream.ReadFully(Stream stream, Byte[] buffer, Int32 offset,
Int32 count)
MySql.Data.MySqlClient.MySqlStream.LoadPacket()
Outer Exception Reading from the stream has failed.
...

(Bug #53457)

After a timeout exception, if an attempt was made to reuse a connection returned to the connection pool the following exception was generated:

[MySqlException (0x80004005): There is already an open DataReader associated with this
Connection which must be closed first.]
   MySql.Data.MySqlClient.MySqlCommand.CheckState() +278
   MySql.Data.MySqlClient.MySqlCommand.ExecuteReader(CommandBehavior behavior) +43
   MySql.Data.MySqlClient.MySqlCommand.ExecuteReader() +6
   Controls.SimpleCommand.ExecuteReader(String SQL) in ...:323
   Albums.GetImagesByAlbum(SimpleCommand Cmd, Int32 iAlbum, String Order, String Limit)
in ...:13
   Forecast.Page_Load(Object sender, EventArgs e) in ...:70
   System.Web.UI.Control.OnLoad(EventArgs e) +99
   System.Web.UI.Control.LoadRecursive() +50
   System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean
includeStagesAfterAsyncPoint) +627

(Bug #53357)

Membership schema creation failed if the default schema collation was not Latin1. (Bug #53174)

EventLog was not disposed in the SessionState provider. (Bug #52550)

Stored procedure enumeration code generated an error if a procedure was used in a dataset that did not return any resultsets. (Bug #50671)

When an application was subjected to increased concurrent load, MySQL Connector/Net generated the following error when calling stored procedures:

A DataTable named \'Procedure Parameters\'
already belongs to this DataSet.

(Bug #49118)

In the ADO.NET Entity Data Model Wizard, the time to update a model scaled abnormally as the number of entities increased. (Bug #48791, Bug #12596237)

The INSERT command was significantly slower with MySQL Connector/Net 6.x compared to 5.x, when compression was enabled. (Bug #48243)

When the connection string option “Connection Reset = True” was used, a connection reset used the previously used encoding for the subsequent authentication operation. This failed, for example, if UCS2 was used to read the last column before the reset. (Bug #47153)

Opening a connection in the Visual Studio Server Explorer and choosing to alter an existing routine required another authentication at the server. (Bug #44715)

When batching was used in MySqlDataAdapter, a connection was not opened automatically in MySqlDataAdapter.Update(). This resulted in an InvalidOperationException exception being generated, with the message text “connection must be valid and open”.

MySQL Connector/Net has been changed to behave more like SQL Server: if the connection is closed, it is opened for the duration of update operation. (Bug #38411)

Database name was emitted into typed datasets. This prevented users using the configured default database. (Bug #33870)

Functionality Added or Changed

Bugs Fixed

Procedure caching had a problem whereby if you created a procedure, dropped it, and recreated it with a different number of parameters an exception was generated.

MySQL Connector/Net has been changed so that if the procedure is recreated with a different number of parameters, it will still be recognized. (Bug #52562)

MySQL Connector/Net has been changed to include MySqlDataReader.GetFieldType(string columnname). Further, MySqlDataReader.GetOrdinal() now includes the name of the column in the exception if the column is not found. (Bug #47467)

If using MySQL Server 5.0.x it was not possible to alter stored routines in Visual Studio. If the stored routine was clicked, and the context sensitive menu option, Alter Routine, selected, the following error was generated:

Unable to load object with error: Object reference not
set to an instance of an object

(Bug #55170)

In MySQL Connector/Net, the MySqlConnection.Abort() method contained a try...catch construct, with an empty catch block. This meant that any exception generated at this point would not be caught. (Bug #52769)

If FunctionsReturnString=true was used in the connection string, the decimal separator (according to locale) was not interpreted. (Bug #52187)

In MySQL Connector/Net, the LoadCharsetMap() function of the CharSetMap class set the following incorrect mapping:

mapping.Add("latin1", new CharacterSet("latin1", 1));

This meant that, for example, the Euro sign was not handled correctly.

The correct mapping should have been:

mapping.Add("latin1", new CharacterSet("windows-1252", 1));

This is because the MySQL latin1 character set is the same as the windows-cp1252 character set and it extends the official ISO 8859-1 or IANA latin1. (Bug #51927)

A non-terminated string in SQL threw a CLR exception rather than a syntax exception. (Bug #51788)

When calling ExecuteNonQuery on a command object, the following exception occurred:

Index and length must refer to a location within the string.
Parameter name: length

(Bug #51610)

The method Command.TrimSemicolons used StringBuilder, and therefore allocated memory for the query even if it did not need to be trimmed. This led to excessive memory consumption when executing a number of large queries. (Bug #51149)

MySqlCommand.Parameters.Clear() did not work. (Bug #50444)

When the MySqlScript.execute() method was called, the following exception was generated:

InvalidOperationException : The CommandText property has not been properly initialized.

(Bug #50344)

Binary Columns were not displayed in the Query Builder of Visual Studio. (Bug #50171)

When the UpdateBatchSize property was set to a value greater than 1, only the first row was applied to the database. (Bug #50123)

When using table per type inheritance and listing the contents of the parent table, the result of the query was a list of child objects, even though there was no related child record with the same parent Id. (Bug #49850)

MySqlDataReader.GetUInt64 returned an incorrect value when reading a BIGINT UNSIGNED column containing a value greater than 2147483647. (Bug #49794)

A FormatException was generated when an empty string was returned from a stored function. (Bug #49642)

When adding a data set in Visual Studio 2008, the following error was generated:

Relations couldn't be added. Column 'REFERENCED_TABLE_CATALOG' does not belong to table.

This was due to a 'REFERENCED_TABLE_CATALOG' column not being included in the foreign keys collection. (Bug #48974)

Attempting to execute a load data local infile on a file where the user did not have write permissions, or the file was open in an editor gave an access denied error. (Bug #48944)

The method MySqlDataReader.GetSchemaTable() returned 0 in the NumericPrecision field for decimal and newdecimal columns. (Bug #48171)

When trying to create stored procedures from an SQL script, a MySqlException was thrown when attempting to redefine the DELIMITER:

MySql.Data.MySqlClient.MySqlException was unhandled
Message="You have an error in your SQL syntax; check the manual that corresponds to your
MySQL server version for the right syntax to use near 'DELIMITER' at line 1"
Source="MySql.Data"
ErrorCode=-2147467259
Number=1064
StackTrace:
à MySql.Data.MySqlClient.MySqlStream.ReadPacket()
à MySql.Data.MySqlClient.NativeDriver.ReadResult(UInt64& affectedRows, Int64&
lastInsertId)
à MySql.Data.MySqlClient.MySqlDataReader.GetResultSet()
à MySql.Data.MySqlClient.MySqlDataReader.NextResult()
à MySql.Data.MySqlClient.MySqlCommand.ExecuteReader(CommandBehavior behavior)
à MySql.Data.MySqlClient.MySqlCommand.ExecuteReader()
à MySql.Data.MySqlClient.MySqlCommand.ExecuteNonQuery()
à MySql.Data.MySqlClient.MySqlScript.Execute()

Note: The MySqlScript class has been fixed to support the delimiter statement as it is found in SQL scripts. (Bug #46429)

Calling a User Defined Function using Entity SQL in the Entity Framework caused a NullReferenceException. (Bug #45277)

A connection string set in web.config could not be reused after Visual Studio 2008 Professional was shut down. It continued working for the existing controls, but did not work for new controls added. (Bug #41629)

Cloning of MySqlCommand was not typesafe. To clone a MySqlCommand it was necessary to do:

MySqlCommand clone = (MySqlCommand)((ICloneable)comm).Clone();

MySQL Connector/Net was changed so that it was possible to do:

MySqlCommand clone = comm.Clone();

(Bug #48460)

If MySqlConnection.GetSchema was called for "Indexes" on a table named “b`a`d” as follows:

DataTable schemaPrimaryKeys = connection.GetSchema(
  "Indexes",
  new string[] { null, schemaName, "b`a`d"});

Then the following exception was generated:

You have an error in your SQL syntax; check the manual that corresponds to
your MySQL server version for the right syntax to use near 'a`d`' at line 1

(Bug #48101)

It was not possible to retrieve a value from a MySQL server table, if the value was larger than that supported by the .NET type System.Decimal.

MySQL Connector/Net was changed to expose the MySqlDecimal type, along with the supporting method GetMySqlDecimal. (Bug #48100)

An entity model created from a schema containing a table with a column of type UNSIGNED BIGINT and a view of the table did not behave correctly. When an entity was created and mapped to the view, the column that was of type UNSIGNED BIGINT was displayed as BIGINT. (Bug #47872)

When loading the MySQLClient-mono.sln file included with the Connector/Net source into Mono Develop, the following error occurred:

/home/tbedford/connector-net-src/6.1/MySQLClient-mono.sln(22):
Unsupported or unrecognized project:
'/home/tbedford/connector-net-src/6.1/Installer/Installer.wixproj'

If the file was modified to remove this problem, then attempting to build the solution generated the following error:

/home/tbedford/connector-net-src/6.1/MySql.Data/Provider/Source/Connection.cs(280,46):
error CS0115: `MySql.Data.MySqlClient.MySqlConnection.DbProviderFactory' is marked as an
override but no suitable property found to override

(Bug #47048)

If an error occurred during connection to a MySQL Server, deserializing the error message from the packet buffer caused a NullReferenceException to be thrown. When the method MySqlPacket::ReadString() attempted to retrieve the error message, the following line of code threw the exception:

string s = encoding.GetString(bits, (int)buffer.Position, end - (int)buffer.Position);

This was due to the fact that the encoding field had not been initialized correctly. (Bug #46844)

In the MySqlDataReader class the GetSByte function returned a byte value instead of an sbyte value. (Bug #46620)

The MySQL Connector/Net Profile Provider, MySql.Web.Profile.MySQLProfileProvider, generated an error when running on Mono. When an attempt was made to save a string in Profile.Name the string was not saved to the my_aspnet_Profiles table. If an attempt was made to force the save with Profile.Save() the following error was generated:

Server Error in '/mono' Application

--------------------------------------------------------------------------------

The requested feature is not implemented.
Description: HTTP 500. Error processing request.

Stack Trace:

System.NotImplementedException: The requested feature is not implemented.
at MySql.Data.MySqlClient.MySqlConnection.EnlistTransaction
(System.Transactions.Transaction transaction) [0x00000]
at MySql.Data.MySqlClient.MySqlConnection.Open () [0x00000]
at MySql.Web.Profile.MySQLProfileProvider.SetPropertyValues
(System.Configuration.SettingsContext context,
System.Configuration.SettingsPropertyValueCollection collection) [0x00000]


--------------------------------------------------------------------------------
Version information: Mono Version: 2.0.50727.1433; ASP.NET Version: 2.0.50727.1433

(Bug #46375)

An exception was generated when using TIMESTAMP columns with the Entity Framework. (Bug #46311)

MySQL Connector/Net sometimes hung, without generating an exception. This happened if a read from a stream failed returning a 0, causing the code in LoadPacket() to enter an infinite loop. (Bug #46308)

When using MySQL Connector/Net 6.0.4 and a MySQL Server 4.1 an exception was generated when trying to execute:

connection.GetSchema("Columns", ...);

The exception generated was:

'connection.GetSchema("Columns")' threw an exception of type
'System.ArgumentException'System.Data.DataTable {System.ArgumentException}
base{"Input string was not in a correct format.Couldn't store <'Select'> in
NUMERIC_PRECISION Column.  Expected type is UInt64."}System.Exception
{System.ArgumentException}

(Bug #46270)

The MySQL Connector/Net method StoredProcedure.GetParameters(string) ignored the programmer's setting of the UseProcedureBodies option. This broke any application for which the application's parameter names did not match the parameter names in the Stored Procedure, resulting in an ArgumentException with the message “Parameter 'foo' not found in the collection.” and the following stack trace:

MySql.Data.dll!MySql.Data.MySqlClient.MySqlParameterCollection.GetParameterFlexible(stri
ng parameterName = "pStart", bool throwOnNotFound = true) Line 459C#
MySql.Data.dll!MySql.Data.MySqlClient.StoredProcedure.Resolve() Line 157 + 0x25
bytesC#
MySql.Data.dll!MySql.Data.MySqlClient.MySqlCommand.ExecuteReader(System.Data.CommandBeha
vior behavior = SequentialAccess) Line 405 + 0xb bytesC#
MySql.Data.dll!MySql.Data.MySqlClient.MySqlCommand.ExecuteDbDataReader(System.Data.Comma
ndBehavior behavior = SequentialAccess) Line 884 + 0xb bytesC#
System.Data.dll!System.Data.Common.DbCommand.System.Data.IDbCommand.ExecuteReader(System
.Data.CommandBehavior behavior) + 0xb bytes
System.Data.dll!System.Data.Common.DbDataAdapter.FillInternal(System.Data.DataSet
dataset = {System.Data.DataSet}, System.Data.DataTable[] datatables = null, int
startRecord = 0, int maxRecords = 0, string srcTable = "Table", System.Data.IDbCommand
command = {MySql.Data.MySqlClient.MySqlCommand}, System.Data.CommandBehavior behavior) +
0x83 bytes
System.Data.dll!System.Data.Common.DbDataAdapter.Fill(System.Data.DataSet dataSet, int
startRecord, int maxRecords, string srcTable, System.Data.IDbCommand command,
System.Data.CommandBehavior behavior) + 0x120 bytes
System.Data.dll!System.Data.Common.DbDataAdapter.Fill(System.Data.DataSet dataSet) +
0x5f bytes

(Bug #46213)

Conversion of MySQL TINYINT(1) to boolean failed. (Bug #46205, Bug #46359, Bug #41953)

When populating a MySQL database table in Visual Studio using the Table Editor, if a VARCHAR(10) column was changed to a VARCHAR(20) column an exception was generated:

SystemArgumentException: DataGridViewComboBoxCell value is not valid.
To replace this default dialog please handle the DataError Event.

(Bug #46100)

In MySQL Connector/Net 6.0.4 using GetProcData generated an error because the parameters data table was only created if MySQL Server was at least version 6.0.6, or if the UseProcedureBodies connection string option was set to true.

Also the DeriveParameters command generated a null reference exception. This was because the parameters data table, which was null, was used in a for each loop. (Bug #45952)

The Entity Framework provider was not calling DBSortExpression correctly when the Skip and Take methods were used, such as in the following statement:

TestModel.tblquarantine.OrderByDescending(q => q.MsgDate).Skip(100).Take(100).ToList();

This resulted in the data being unsorted. (Bug #45723)

The EscapeString code carried out escaping by calling string.Replace multiple times. This resulted in a performance bottleneck, as for every line a new string was allocated and another was disposed of by the garbage collector. (Bug #45699)

Adding the Allow Batch=False option to the connection string caused MySQL Connector/Net to generate the error:

You have an error in your SQL syntax; check the manual that corresponds to your MySQL
server version for the right syntax to use near 'SET character_set_results=NULL' at line 1

(Bug #45502)

The MySQL Connector/Net 6.0.4 installer failed with an error. The error message generated was:

There is a problem with this Windows Installer package. A DLL required for this
install to complete could not be run. Contact your support personnel or package vendor.

When OK was clicked to acknowledge the error the installer exited. (Bug #45474)

A MySQL Connector/Net test program that connected to MySQL Server using the connection string option compress=true crashed, but only when running on Mono. The program worked as expected when running on Microsoft Windows.

This was due to a bug in Mono. MySQL Connector/Net was modified to avoid using WeakReferences in the Compressed stream class, which was causing the crash. (Bug #45463)

Calling the Entity Framework SaveChanges() method of any MySQL ORM Entity with a column type TIME, generated an error message:

Unknown PrimitiveKind Time

(Bug #45457)

Insert into two tables failed when using the Entity Framework. The exception generated was:

The value given is not an instance of type 'Edm.Int32'

(Bug #45077)

Input parameters were missing from Stored Procedures when using them with ADO.NET Data Entities. (Bug #44985)

Errors occurred when using the Entity Framework with cultures that used a comma as the decimal separator. This was because the formatting for SINGLE, DOUBLE and DECIMAL values was not handled correctly. (Bug #44455)

When attempting to connect to MySQL using the Compact Framework version of MySQL Connector/Net, an IndexOutOfRangeException exception was generated on trying to open the connection. (Bug #43736)

When reading data, such as with a MySqlDataAdapter on a MySqlConnection, MySQL Connector/Net could potentially enter an infinite loop in CompressedStream.ReadNextpacket() if compression was enabled. (Bug #43678)

An error occurred when building MySQL Connector/Net from source code checked out from the public SVN repository. This happened on Linux using Mono and Nant. The Mono JIT compiler version was 1.2.6.0. The Nant version was 0.85.

When an attempt was made to build (for example) the MySQL Connector/Net 5.2 branch using the command:

$ nant -buildfile:Client.build

The following error occurred:

BUILD FAILED

Error loading buildfile.
Encoding name 'Windows-1252' not supported.
Parameter name: name

(Bug #42411)

After a Reference to "C:\Program Files\MySQL\MySQL Connector Net 5.2.4\Compact Framework\MySql.Data.CF.dll" was added to a Windows Mobile 5.0 project, the project then failed to build, generating a Microsoft Visual C# compiler error.

The error generated was:

Error 2 The type 'System.Runtime.CompilerServices.CompilerGeneratedAttribute'
has no constructors defined MysqlTest
Error 3 Internal Compiler Error (0xc0000005 at address 5A7E3714):
likely culprit is 'COMPILE'.

(Bug #42261)

MySQL Connector/Net CHM documentation stated that MySQL Server 3.23 was supported. (Bug #42110)

In the case of long network inactivity, especially when connection pooling was used, connections were sometimes dropped, for example, by firewalls.

Note: The bugfix introduced a new keepalive parameter, which prevents disconnects by sending an empty TCP packet after a specified timeout. (Bug #40684)

MySQL Connector/Net generated the following exception:

System.NullReferenceException: Object reference not set to an instance of an object.
      bei MySql.Data.MySqlClient.MySqlCommand.TimeoutExpired(Object commandObject)
      bei System.Threading._TimerCallback.TimerCallback_Context(Object state)
      bei System.Threading.ExecutionContext.runTryCode(Object userData)
      bei
      System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(TryCode
      code, CleanupCode backoutCode, Object userData)
      bei System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext,
      ContextCallback callback, Object state)
      bei System.Threading.ExecutionContext.Run(ExecutionContext executionContext,
      ContextCallback callback, Object state)
      bei System.Threading._TimerCallback.PerformTimerCallback(Object state)

(Bug #40005)

Calling a Stored Procedure with an output parameter through MySQL Connector/Net resulted in a memory leak. Calling the same Stored Procedure without an output parameter did not result in a memory leak. (Bug #36027)

Using a DataAdapter with a linked MySqlCommandBuilder the following exception was thrown when trying to call da.Update(DataRow[] rows):

Connection must be valid and open

(Bug #34657)

If a certain socket exception occurred when trying to establish a MySQL database connection, MySQL Connector/Net displayed an exception message that appeared to be unrelated to the underlying problem. This masked the problem and made diagnosing problems more difficult.

For example, if, when establishing a database connection using TCP/IP, Windows on the local machine allocated an ephemeral port that conflicted with a socket address still in use, then Windows/.NET would throw a socket exception with the following error text:

Only one usage of each socket address (protocol/network address/port) is normally
permitted IP ADDRESS/PORT.

However, MySQL Connector/Net masked this socket exception and displayed an exception with the following text:

Unable to connect to any of the specified MySQL hosts.

(Bug #45021)

An SQL query string containing an escaped backslash caused an exception to be generated:

Index and length must refer to a location within the string.
Parameter name: length
at System.String.InternalSubStringWithChecks(Int32 startIndex, Int32 length, Boolean
fAlwaysCopy)
at MySql.Data.MySqlClient.MySqlTokenizer.NextParameter()
at MySql.Data.MySqlClient.Statement.InternalBindParameters(String sql,
MySqlParameterCollection parameters, MySqlPacket packet)
at MySql.Data.MySqlClient.Statement.BindParameters()
at MySql.Data.MySqlClient.PreparableStatement.Execute()
at MySql.Data.MySqlClient.MySqlCommand.ExecuteReader(CommandBehavior be‎havior)
at MySql.Data.MySqlClient.MySqlCommand.ExecuteNonQuery()

(Bug #44960)

The Microsoft Visual Studio solution file MySQL-VS2005.sln was invalid. Several projects could not be loaded and thus it was not possible to build MySQL Connector/Net from source. (Bug #44822)

The Data Set editor generated an error when attempts were made to modify insert, update or delete commands:

Error in WHERE clause near '@'.
Unable to parse query text.

(Bug #44512)

The DataReader in MySQL Connector/Net 6.0.3 considered a BINARY(16) field as a GUID with a length of 16. (Bug #44507)

When creating a new DataSet the following error was generated:

Failed to open a connection to database.
Cannot load type with name 'MySQL.Data.VisualStudio.StoredProcedureColumnEnumerator'

(Bug #44460)

The MySQL Connector/Net MySQLRoleProvider reported that there were no roles, even when roles existed. (Bug #44414)

MySQL Connector/Net was missing the capability to validate the server's certificate when using encryption. This made it possible to conduct a man-in-the-middle attack against the connection, which defeated the security provided by SSL. (Bug #38700)

Functionality Added or Changed

Bugs Fixed

The MySqlTokenizer failed to split fieldnames from values if they were not separated by a space. This also happened if the string contained certain characters. As a result MySqlCommand.ExecuteNonQuery raised an index out of range exception.

The resulting errors are illustrated by the following examples. Note, the example statements do not have delimiting spaces around the = operator.

INSERT INTO anytable SET Text='test--test';

The tokenizer incorrectly interpreted the value as containing a comment.

UPDATE anytable SET Project='123-456',Text='Can you explain this ?',Duration=15 WHERE
      ID=4711;'

A MySqlException was generated, as the ? in the value was interpreted by the tokenizer as a parameter sign. The error message generated was:

Fatal error encountered during command execution.
EXCEPTION: MySqlException - Parameter '?'' must be defined.

(Bug #44318)

MySQL.Data was not displayed as a Reference inside Microsoft Visual Studio 2008 Professional.

When a new C# project was created in Microsoft Visual Studio 2008 Professional, MySQL.Data was not displayed when References, Add Reference was selected. (Bug #44141)

Column types for SchemaProvider and ISSchemaProvider did not match.

When the source code in SchemaProvider.cs and ISSchemaProvider.cs were compared it was apparent that they were not using the same column types. The base provider used SQL such as SHOW CREATE TABLE, while ISSchemaProvider used the schema information tables. Column types used by the base class were INT64 and the column types used by ISSchemaProvider were UNSIGNED. (Bug #44123)

MySQL Connector/Net 6.0.1 did not load in Microsoft Visual Studio 2008 and Visual Studio 2005 Pro.

The following error message was generated:

.NET Framework Data Provider for MySQL: The data provider object factory service was not
found.

(Bug #44064)

An insert and update error was generated by the decimal data type in the Entity Framework, when a German collation was used. (Bug #43574)

Generating an Entity Data Model (EDM) schema with a table containing columns with data types MEDIUMTEXT and LONGTEXT generated a runtime error message “Max value too long or too short for Int32”. (Bug #43480)

A null reference exception was generated when MySqlConnection.ClearPool(connection) was called. (Bug #42801)

The Web Provider did not work at all on a remote host, and did not create a database when using autogenerateschema="true". (Bug #39072)

The MySQL Connector/Net installer program ended prematurely without reporting the specific error. (Bug #39019)

When called with an incorrect password the MembershipProvider.GetPassword() method threw a MySQLException instead of a MembershipPasswordException . (Bug #38939)

Possible overflow in MySqlPacket.ReadLong(). (Bug #36997)

The TokenizeSql method was adding query overhead and causing high CPU utilization for larger queries. (Bug #36836)

If MySqlConnection.GetSchema was called for "Indexes" on a table named “b`a`d” as follows:

DataTable schemaPrimaryKeys = connection.GetSchema(
  "Indexes",
  new string[] { null, schemaName, "b`a`d"});

Then the following exception was generated:

You have an error in your SQL syntax; check the manual that corresponds to
your MySQL server version for the right syntax to use near 'a`d`' at line 1

(Bug #48101)

When the connection string option “Connection Reset = True” was used, a connection reset used the previously used encoding for the subsequent authentication operation. This failed, for example, if UCS2 was used to read the last column before the reset. (Bug #47153)

In the MySqlDataReader class the GetSByte function returned a byte value instead of an sbyte value. (Bug #46620)

When trying to create stored procedures from an SQL script, a MySqlException was thrown when attempting to redefine the DELIMITER:

MySql.Data.MySqlClient.MySqlException was unhandled
Message="You have an error in your SQL syntax; check the manual that corresponds to your
MySQL server version for the right syntax to use near 'DELIMITER' at line 1"
Source="MySql.Data"
ErrorCode=-2147467259
Number=1064
StackTrace:
à MySql.Data.MySqlClient.MySqlStream.ReadPacket()
à MySql.Data.MySqlClient.NativeDriver.ReadResult(UInt64& affectedRows, Int64&
lastInsertId)
à MySql.Data.MySqlClient.MySqlDataReader.GetResultSet()
à MySql.Data.MySqlClient.MySqlDataReader.NextResult()
à MySql.Data.MySqlClient.MySqlCommand.ExecuteReader(CommandBehavior behavior)
à MySql.Data.MySqlClient.MySqlCommand.ExecuteReader()
à MySql.Data.MySqlClient.MySqlCommand.ExecuteNonQuery()
à MySql.Data.MySqlClient.MySqlScript.Execute()

Note: The MySqlScript class has been fixed to support the delimiter statement as it is found in SQL scripts. (Bug #46429)

The MySQL Connector/Net Profile Provider, MySql.Web.Profile.MySQLProfileProvider, generated an error when running on Mono. When an attempt was made to save a string in Profile.Name the string was not saved to the my_aspnet_Profiles table. If an attempt was made to force the save with Profile.Save() the following error was generated:

Server Error in '/mono' Application

--------------------------------------------------------------------------------

The requested feature is not implemented.
Description: HTTP 500. Error processing request.

Stack Trace:

System.NotImplementedException: The requested feature is not implemented.
at MySql.Data.MySqlClient.MySqlConnection.EnlistTransaction
(System.Transactions.Transaction transaction) [0x00000]
at MySql.Data.MySqlClient.MySqlConnection.Open () [0x00000]
at MySql.Web.Profile.MySQLProfileProvider.SetPropertyValues
(System.Configuration.SettingsContext context,
System.Configuration.SettingsPropertyValueCollection collection) [0x00000]


--------------------------------------------------------------------------------
Version information: Mono Version: 2.0.50727.1433; ASP.NET Version: 2.0.50727.1433

(Bug #46375)

When using MySQL Connector/Net 6.0.4 and a MySQL Server 4.1 an exception was generated when trying to execute:

connection.GetSchema("Columns", ...);

The exception generated was:

'connection.GetSchema("Columns")' threw an exception of type
'System.ArgumentException'System.Data.DataTable {System.ArgumentException}
base{"Input string was not in a correct format.Couldn't store <'Select'> in
NUMERIC_PRECISION Column.  Expected type is UInt64."}System.Exception
{System.ArgumentException}

(Bug #46270)

The MySQL Connector/Net method StoredProcedure.GetParameters(string) ignored the programmer's setting of the UseProcedureBodies option. This broke any application for which the application's parameter names did not match the parameter names in the Stored Procedure, resulting in an ArgumentException with the message “Parameter 'foo' not found in the collection.” and the following stack trace:

MySql.Data.dll!MySql.Data.MySqlClient.MySqlParameterCollection.GetParameterFlexible(stri
ng parameterName = "pStart", bool throwOnNotFound = true) Line 459C#
MySql.Data.dll!MySql.Data.MySqlClient.StoredProcedure.Resolve() Line 157 + 0x25
bytesC#
MySql.Data.dll!MySql.Data.MySqlClient.MySqlCommand.ExecuteReader(System.Data.CommandBeha
vior behavior = SequentialAccess) Line 405 + 0xb bytesC#
MySql.Data.dll!MySql.Data.MySqlClient.MySqlCommand.ExecuteDbDataReader(System.Data.Comma
ndBehavior behavior = SequentialAccess) Line 884 + 0xb bytesC#
System.Data.dll!System.Data.Common.DbCommand.System.Data.IDbCommand.ExecuteReader(System
.Data.CommandBehavior behavior) + 0xb bytes
System.Data.dll!System.Data.Common.DbDataAdapter.FillInternal(System.Data.DataSet
dataset = {System.Data.DataSet}, System.Data.DataTable[] datatables = null, int
startRecord = 0, int maxRecords = 0, string srcTable = "Table", System.Data.IDbCommand
command = {MySql.Data.MySqlClient.MySqlCommand}, System.Data.CommandBehavior behavior) +
0x83 bytes
System.Data.dll!System.Data.Common.DbDataAdapter.Fill(System.Data.DataSet dataSet, int
startRecord, int maxRecords, string srcTable, System.Data.IDbCommand command,
System.Data.CommandBehavior behavior) + 0x120 bytes
System.Data.dll!System.Data.Common.DbDataAdapter.Fill(System.Data.DataSet dataSet) +
0x5f bytes

(Bug #46213)

Conversion of MySQL TINYINT(1) to boolean failed. (Bug #46205, Bug #46359, Bug #41953)

If the application slept for longer than the specified net_write_timeout, and then resumed Read operations on a connection, then the application failed silently. (Bug #45978)

When reading data, such as with a MySqlDataAdapter on a MySqlConnection, MySQL Connector/Net could potentially enter an infinite loop in CompressedStream.ReadNextpacket() if compression was enabled. (Bug #43678)

An error occurred when building MySQL Connector/Net from source code checked out from the public SVN repository. This happened on Linux using Mono and Nant. The Mono JIT compiler version was 1.2.6.0. The Nant version was 0.85.

When an attempt was made to build (for example) the MySQL Connector/Net 5.2 branch using the command:

$ nant -buildfile:Client.build

The following error occurred:

BUILD FAILED

Error loading buildfile.
Encoding name 'Windows-1252' not supported.
Parameter name: name

(Bug #42411)

MySQL Connector/Net CHM documentation stated that MySQL Server 3.23 was supported. (Bug #42110)

Using a DataAdapter with a linked MySqlCommandBuilder the following exception was thrown when trying to call da.Update(DataRow[] rows):

Connection must be valid and open

(Bug #34657)

The EscapeString code carried out escaping by calling string.Replace multiple times. This resulted in a performance bottleneck, as for every line a new string was allocated and another was disposed of by the garbage collector. (Bug #45699)

A MySQL Connector/Net test program that connected to MySQL Server using the connection string option compress=true crashed, but only when running on Mono. The program worked as expected when running on Microsoft Windows.

This was due to a bug in Mono. MySQL Connector/Net was modified to avoid using WeakReferences in the Compressed stream class, which was causing the crash. (Bug #45463)

If a certain socket exception occurred when trying to establish a MySQL database connection, MySQL Connector/Net displayed an exception message that appeared to be unrelated to the underlying problem. This masked the problem and made diagnosing problems more difficult.

For example, if, when establishing a database connection using TCP/IP, Windows on the local machine allocated an ephemeral port that conflicted with a socket address still in use, then Windows/.NET would throw a socket exception with the following error text:

Only one usage of each socket address (protocol/network address/port) is normally
permitted IP ADDRESS/PORT.

However, MySQL Connector/Net masked this socket exception and displayed an exception with the following text:

Unable to connect to any of the specified MySQL hosts.

(Bug #45021)

The Microsoft Visual Studio solution file MySQL-VS2005.sln was invalid. Several projects could not be loaded and thus it was not possible to build MySQL Connector/Net from source. (Bug #44822)

The MySQL Connector/Net MySQLRoleProvider reported that there were no roles, even when roles existed. (Bug #44414)

After a Reference to "C:\Program Files\MySQL\MySQL Connector Net 5.2.4\Compact Framework\MySql.Data.CF.dll" was added to a Windows Mobile 5.0 project, the project then failed to build, generating a Microsoft Visual C# compiler error.

The error generated was:

Error 2 The type 'System.Runtime.CompilerServices.CompilerGeneratedAttribute'
has no constructors defined MysqlTest
Error 3 Internal Compiler Error (0xc0000005 at address 5A7E3714):
likely culprit is 'COMPILE'.

(Bug #42261)

MySQL Connector/Net generated the following exception:

System.NullReferenceException: Object reference not set to an instance of an object.
      bei MySql.Data.MySqlClient.MySqlCommand.TimeoutExpired(Object commandObject)
      bei System.Threading._TimerCallback.TimerCallback_Context(Object state)
      bei System.Threading.ExecutionContext.runTryCode(Object userData)
      bei
      System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(TryCode
      code, CleanupCode backoutCode, Object userData)
      bei System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext,
      ContextCallback callback, Object state)
      bei System.Threading.ExecutionContext.Run(ExecutionContext executionContext,
      ContextCallback callback, Object state)
      bei System.Threading._TimerCallback.PerformTimerCallback(Object state)

(Bug #40005)

When a TableAdapter was created on a DataSet, it was not possible to use a stored procedure with variables. The following error was generated:

The method or operation is not implemented

(Bug #39409)

Functionality Added or Changed

Bugs Fixed

A new connection string option has been added: use affected rows. When true the connection will report changed rows instead of found rows. (Bug #44194)

Calling GetSchema() on Indexes or IndexColumns failed where index or column names were restricted.

In SchemaProvider.cs, methods GetIndexes() and GetIndexColumns() passed their restrictions directly to GetTables(). This only worked if the restrictions were no more specific than schemaName and tableName. If IndexName was given, this was passed to GetTables() where it was treated as TableType. As a result no tables were returned, unless the index name happened to be BASE TABLE or VIEW. This meant that both methods failed to return any rows. (Bug #43991)

GetSchema("MetaDataCollections") should have returned a table with a column named “NumberOfRestrictions” not “NumberOfRestriction”.

This can be confirmed by referencing the Microsoft Documentation. (Bug #43990)

Requests sent to the MySQL Connector/Net role provider to remove a user from a role failed. The query log showed the query was correctly executed within a transaction which was immediately rolled back. The rollback was caused by a missing call to the Complete method of the transaction. (Bug #43553)

When using MySqlBulkLoader.Load(), the text file is opened by NativeDriver.SendFileToServer. If it encountered a problem opening the file as a stream, an exception was generated and caught. An attempt to clean up resources was then made in the finally{} clause by calling fs.Close(), but since the stream was never successfully opened, this was an attempt to execute a method of a null reference. (Bug #43332)

A null reference exception was generated when MySqlConnection.ClearPool(connection) was called. (Bug #42801)

MySQLMembershipProvider.ValidateUser only used the userId to validate. However, it should also use the applicationId to perform the validation correctly.

The generated query was, for example:

SELECT Password, PasswordKey, PasswordFormat, IsApproved, Islockedout
      FROM my_aspnet_Membership WHERE userId=13

Note that applicationId is not used. (Bug #42574)

There was an error in the ProfileProvider class in the private ProfileInfoCollection GetProfiles() function. The column of the final table was named “lastUpdatdDate” ('e' is missing) instead of the correct “lastUpdatedDate”. (Bug #41654)

The GetGuid() method of MySqlDataReader did not treat BINARY(16) column data as a GUID. When operating on such a column a FormatException exception was generated. (Bug #41452)

When ASP.NET membership was configured to not require password question and answer using requiresQuestionAndAnswer="false", a SqlNullValueException was generated when using MembershipUser.ResetPassword() to reset the user password. (Bug #41408)

If a Stored Procedure contained spaces in its parameter list, and was then called from MySQL Connector/Net, an exception was generated. However, the same Stored Procedure called from the MySQL Query Analyzer or the MySQL Client worked correctly.

The exception generated was:

Parameter '0' not found in the collection.

(Bug #41034)

The DATETIME format contained an erroneous space. (Bug #41021)

When MySql.Web.Profile.MySQLProfileProvider was configured, it was not possible to assign a name other than the default name MySQLProfileProvider.

If the name SCC_MySQLProfileProvider was assigned, an exception was generated when attempting to use Page.Context.Profile['custom prop'].

The exception generated was:

The profile default provider was not found.

Note that the exception stated: 'the profile default provider...', even though a different name was explicitly requested. (Bug #40871)

When ExecuteNonQuery was called with a command type of Stored Procedure it worked for one user but resulted in a hang for another user with the same database permissions.

However, if CALL was used in the command text and ExecuteNonQuery was used with a command type of Text, the call worked for both users. (Bug #40139)

Visual Studio 2008 displayed the following error three times on start-up:

"Package Load Failure

Package 'MySql.Data.VisualStudio.MySqlDataProviderPackage, MySql.VisualStudio,
Version=5.2.4, Culture=neutral, PublicKeyToken=null' has failed to load properly (GUID =
{79A115C9-B133-4891-9E7B-242509DAD272}).  Please contact the package vendor for
assistance.  Application restart is recommended, due to possible environment corruption.
Would you like to disable loading the package in the future?  You may use
'devenve/resetskippkgs' to re-enable package loading."

(Bug #40726)

MySqlDataReader did not feature a GetSByte method. (Bug #40571)

When working with stored procedures MySQL Connector/Net generated an exception Unknown "table parameters" in information_schema. (Bug #40382)

GetDefaultCollation and GetMaxLength were not thread safe. These functions called the database to get a set of parameters and cached them in two static dictionaries in the function InitCollections. However, if many threads called them they would try to insert the same keys in the collections resulting in duplicate key exceptions. (Bug #40231)

If connection pooling was not set explicitly in the connection string, MySQL Connector/Net added “;Pooling=False” to the end of the connection string when MySqlCommand.ExecuteReader() was called.

If connection pooling was explicitly set in the connection string, when MySqlConnection.Open() was called it converted “Pooling=True” to “pooling=True”.

If MySqlCommand.ExecuteReader() was subsequently called, it concatenated “;Pooling=False” to the end of the connection string. The resulting connection string was thus terminated with “pooling=True;Pooling=False”. This disabled connection pooling completely. (Bug #40091)

The connection string option Functions Return String did not set the correct encoding for the result string. Even though the connection string option Functions Return String=true; is set, the result of SELECT DES_DECRYPT() contained “??” instead of the correct national character symbols. (Bug #40076)

If, when using the MySqlTransaction transaction object, an exception was thrown, the transaction object was not disposed of and the transaction was not rolled back. (Bug #39817)

After the ConnectionString property was initialized using the public setter of DbConnectionStringBuilder, the GetConnectionString method of MySqlConnectionStringBuilder incorrectly returned null when true was assigned to the includePass parameter. (Bug #39728)

When using ProfileProvider, attempting to update a previously saved property failed. (Bug #39330)

Reading a negative time value greater than -01:00:00 returned the absolute value of the original time value. (Bug #39294)

Inserting a negative time value (negative TimeSpan) into a Time column through the use of MySqlParameter caused MySqlException to be thrown. (Bug #39275)

When a data connection was created in the server explorer of Visual Studio 2008 Team, an error was generated when trying to expand stored procedures that had parameters.

Also, if TableAdapter was right-clicked and then Add, Query, Use Existing Stored Procedures selected, if you then attempted to select a stored procedure, the window would close and no error message would be displayed. (Bug #39252)

The Web Provider did not work at all on a remote host, and did not create a database when using autogenerateschema="true". (Bug #39072)

MySQL Connector/Net called hashed password methods not supported in Mono 2.0 Preview 2. (Bug #38895)

Functionality Added or Changed

Bugs Fixed

Error string was returned after a 28000 second wait_timeout. This has been changed to generate a ConnectionState.Closed event. (Bug #38119)

Changed how the procedure schema collection is retrieved. If use procedure bodies=true then the mysql.proc table is selected directly as this is up to 50 times faster than the current information_schema implementation. If use procedure bodies=false, then the information_schema collection is queried. (Bug #36694)

String escaping functionality has been moved from the MySqlString class to the MySqlHelper class, where it can be accessed by the EscapeString method. (Bug #36205)

The GetOrdinal() method failed to return the ordinal if the column name string contained an accent. (Bug #38721)

MySQL Connector/Net uninstaller did not clean up all installed files. (Bug #38534)

There was a short circuit evaluation error in the MySqlCommand.CheckState() method. When the statement connection == null was true a NullReferenceException was thrown and not the expected InvalidOperationException. (Bug #38276)

The provider did not silently create the user if the user did not exist. (Bug #38243)

Executing a command that resulted in a fatal exception did not close the connection. (Bug #37991)

When a prepared insert query is run that contains an UNSIGNED TINYINT in the parameter list, the complete query and data that should be inserted is corrupted and no error is thrown. (Bug #37968)

In a .NET application MySQL Connector/Net modifies the connection string so that it contains several occurrences of the same option with different values. This is illustrated by the example that follows.

The original connection string:

host=localhost;database=test;uid=*****;pwd=*****;
connect timeout=25; auto enlist=false;pooling=false;

The connection string after closing MySqlDataReader:

host=localhost;database=test;uid=*****;pwd=*****;
connect timeout=25;auto enlist=false;pooling=false;
Allow User Variables=True;Allow User Variables=False;
Allow User Variables=True;Allow User Variables=False;

(Bug #37955)

Unnecessary network traffic was generated for the normal case where the web provider schema was up to date. (Bug #37469)

MySqlReader.GetOrdinal() performance enhancements break existing functionality. (Bug #37239)

The autogenerateschema option produced tables with incorrect collations. (Bug #36444)

GetSchema did not work correctly when querying for a collection, if using a non-English locale. (Bug #35459)

When reading back a stored double or single value using the .NET provider, the value had less precision than the one stored. (Bug #33322)

Using the MySQL Visual Studio plugin and a MySQL 4.1 server, certain field types (ENUM) would not be identified correctly. Also, when looking for tables, the plugin would list all tables matching a wildcard pattern of the database name supplied in the connection string, instead of only tables within the specified database. (Bug #30603)

Product documentation incorrectly stated '?' is the preferred parameter marker. (Bug #37349)

An incorrect value for a bit field would returned in a multi-row query if a preceding value for the field returned NULL. (Bug #36313)

Tables with GEOMETRY field types would return an unknown data type exception. (Bug #36081)

When using the MySQLProfileProvider, setting profile details and then reading back saved data would result in the default values being returned instead of the updated values. (Bug #36000)

When creating a connection, setting the ConnectionString property of MySqlConnection to NULL would throw an exception. (Bug #35619)

The DbCommandBuilder.QuoteIdentifer method was not implemented. (Bug #35492)

When using encrypted passwords, the GetPassword() function would return the wrong string. (Bug #35336)

An error would be raised when calling GetPassword() with a NULL value. (Bug #35332)

When retrieving data where a field has been identified as containing a GUID value, the incorrect value would be returned when a previous row contained a NULL value for that field. (Bug #35041)

Using the TableAdapter Wizard failed when generating commands that used stored procedures due to the change in supported parameter characters. (Bug #34941)

When creating a new stored procedures, the new parameter code which permits the use of the @ symbol would interfere with the specification of a DEFINER. (Bug #34940)

When using SqlDataSource to open a connection, the connection would not automatically be closed when access had completed. (Bug #34460)

There was a high level of contention in the connection pooling code that could lead to delays when opening connections and submitting queries. The connection pooling code has been modified to try and limit the effects of the contention issue. (Bug #34001)

Using the TableAdapter wizard in combination with a suitable SELECT statement, only the associated INSERT statement would also be created, rather than the required DELETE and UPDATE statements. (Bug #31338)

Fixed problem in datagrid code related to creating a new table. This problem may have been introduced with .NET 2.0 SP1.

Fixed profile provider that would throw an exception if you were updating a profile that already existed.

When using the provider to generate or update users and passwords, the password checking algorithm would not validate the password strength or requirements correctly. (Bug #34792)

When executing statements that used stored procedures and functions, the new parameter code could fail to identify the correct parameter format. (Bug #34699)

The installer failed to the DDEX provider binary if the Visual Studio 2005 component was not selected. The result would lead to MySQL Connector/Net not loading properly when using the interface to a MySQL server within Visual Studio. (Bug #34674)

A number of issues were identified in the case, connection and schema areas of the code for MembershipProvider, RoleProvider, ProfileProvider. (Bug #34495)

When using web providers, the MySQL Connector/Net would check the schema and cache the application id, even when the connection string had been set. The effect would be to break the membership provider list. (Bug #34451)

Attempting to use an isolation level other than the default with a transaction scope would use the default isolation level. (Bug #34448)

When altering a stored procedure within Visual Studio, the parameters to the procedure could be lost. (Bug #34359)

A race condition could occur within the procedure cache resulting the cache contents overflowing beyond the configured cache size. (Bug #34338)

Fixed problem with Visual Studio 2008 integration that caused pop-up menus on server explorer nodes to not function

The provider code has been updated to fix a number of outstanding issues.

Functionality Added or Changed

Bugs Fixed

Performing GetValue() on a field TINYINT(1) returned a BOOLEAN. While not a bug, this caused problems in software that expected an INT to be returned. A new connection string option Treat Tiny As Boolean has been added with a default value of true. If set to false the provider will treat TINYINT(1) as INT. (Bug #34052)

Added support for DbDataAdapter UpdateBatchSize. Batching is fully supported including collapsing inserts down into the multi-value form if possible.

DDEX provider now works under Visual Studio 2008 beta 2.

Added ClearPool and ClearAllPools features.

Some speed improvements have been implemented in the TokenizeSql process used to identify elements of SQL statements. (Bug #34220)

When accessing tables from different databases within the same TransactionScope, the same user/password combination would be used for each database connection. MySQL Connector/Net does not handle multiple connections within the same transaction scope. An error is now returned if you attempt this process, instead of using the incorrect authorization information. (Bug #34204)

The status of connections reported through the state change handler was not being updated correctly. (Bug #34082)

Incorporated some connection string cache optimizations sent to us by Maxim Mass. (Bug #34000)

In an open connection where the server had disconnected unexpectedly, the status information of the connection would not be updated properly. (Bug #33909)

Data cached from the connection string could return invalid information because the internal routines were not using case-sensitive semantics. This lead to updated connection string options not being recognized if they were of a different case than the existing cached values. (Bug #31433)

Column name metadata was not using the character set as defined within the connection string being used. (Bug #31185)

Memory usage could increase and decrease significantly when updating or inserting a large number of rows. (Bug #31090)

Commands executed from within the state change handler would fail with a NULL exception. (Bug #30964)

When running a stored procedure multiple times on the same connection, the memory usage could increase indefinitely. (Bug #30116)

Using compression in the MySQL connection with MySQL Connector/Net would be slower than using native (uncompressed) communication. (Bug #27865)

The MySqlDbType.Datetime has been replaced with MySqlDbType.DateTime. The old format has been obsoleted. (Bug #26344)

Calling GetSchema() on Indexes or IndexColumns failed where index or column names were restricted.

In SchemaProvider.cs, methods GetIndexes() and GetIndexColumns() passed their restrictions directly to GetTables(). This only worked if the restrictions were no more specific than schemaName and tableName. If IndexName was given, this was passed to GetTables() where it was treated as TableType. As a result no tables were returned, unless the index name happened to be BASE TABLE or VIEW. This meant that both methods failed to return any rows. (Bug #43991)

The DATETIME format contained an erroneous space. (Bug #41021)

If connection pooling was not set explicitly in the connection string, MySQL Connector/Net added “;Pooling=False” to the end of the connection string when MySqlCommand.ExecuteReader() was called.

If connection pooling was explicitly set in the connection string, when MySqlConnection.Open() was called it converted “Pooling=True” to “pooling=True”.

If MySqlCommand.ExecuteReader() was subsequently called, it concatenated “;Pooling=False” to the end of the connection string. The resulting connection string was thus terminated with “pooling=True;Pooling=False”. This disabled connection pooling completely. (Bug #40091)

MySQL Connector/Net generated the following exception:

System.NullReferenceException: Object reference not set to an instance of an object.
      bei MySql.Data.MySqlClient.MySqlCommand.TimeoutExpired(Object commandObject)
      bei System.Threading._TimerCallback.TimerCallback_Context(Object state)
      bei System.Threading.ExecutionContext.runTryCode(Object userData)
      bei
      System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(TryCode
      code, CleanupCode backoutCode, Object userData)
      bei System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext,
      ContextCallback callback, Object state)
      bei System.Threading.ExecutionContext.Run(ExecutionContext executionContext,
      ContextCallback callback, Object state)
      bei System.Threading._TimerCallback.PerformTimerCallback(Object state)

(Bug #40005)

If, when using the MySqlTransaction transaction object, an exception was thrown, the transaction object was not disposed of and the transaction was not rolled back. (Bug #39817)

When a prepared insert query is run that contains an UNSIGNED TINYINT in the parameter list, the complete query and data that should be inserted is corrupted and no error is thrown. (Bug #37968)

Calling MySqlDataAdapter.FillSchema on a SELECT statement that referred to a table that did not exist left the connection in a bad state. After this call, all SELECT statements returned an empty result set. If the SELECT statement referred to a table that did exist then everything worked as expected. (Bug #30518)

There was a short circuit evaluation error in the MySqlCommand.CheckState() method. When the statement connection == null was true a NullReferenceException was thrown and not the expected InvalidOperationException. (Bug #38276)

Executing a command that resulted in a fatal exception did not close the connection. (Bug #37991)

In a .NET application MySQL Connector/Net modifies the connection string so that it contains several occurrences of the same option with different values. This is illustrated by the example that follows.

The original connection string:

host=localhost;database=test;uid=*****;pwd=*****;
connect timeout=25; auto enlist=false;pooling=false;

The connection string after closing MySqlDataReader:

host=localhost;database=test;uid=*****;pwd=*****;
connect timeout=25;auto enlist=false;pooling=false;
Allow User Variables=True;Allow User Variables=False;
Allow User Variables=True;Allow User Variables=False;

(Bug #37955)

As MySqlDbType.DateTime is not available in VB.Net the warning The datetime enum value is obsolete was always shown during compilation. (Bug #37406)

An unknown MySqlErrorCode was encountered when opening a connection with an incorrect password. (Bug #37398)

Documentation incorrectly stated that “the DataColumn class in .NET 1.0 and 1.1 does not permit columns with type of UInt16, UInt32, or UInt64 to be autoincrement columns”. (Bug #37350)

SemaphoreFullException is generated when application is closed. (Bug #36688)

GetSchema did not work correctly when querying for a collection, if using a non-English locale. (Bug #35459)

When reading back a stored double or single value using the .NET provider, the value had less precision than the one stored. (Bug #33322)

Using the MySQL Visual Studio plugin and a MySQL 4.1 server, certain field types (ENUM) would not be identified correctly. Also, when looking for tables, the plugin would list all tables matching a wildcard pattern of the database name supplied in the connection string, instead of only tables within the specified database. (Bug #30603)

When creating a connection pool, specifying an invalid IP address will cause the entire application to crash, instead of providing an exception. (Bug #36432)

An incorrect value for a bit field would returned in a multi-row query if a preceding value for the field returned NULL. (Bug #36313)

The MembershipProvider will raise an exception when the connection string is configured with enablePasswordRetrival = true and RequireQuestionAndAnswer = false. (Bug #36159)

When calling GetNumberOfUsersOnline an exception is raised on the submitted query due to a missing parameter. (Bug #36157)

Tables with GEOMETRY field types would return an unknown data type exception. (Bug #36081)

When creating a connection, setting the ConnectionString property of MySqlConnection to NULL would throw an exception. (Bug #35619)

The DbCommandBuilder.QuoteIdentifer method was not implemented. (Bug #35492)

When using SqlDataSource to open a connection, the connection would not automatically be closed when access had completed. (Bug #34460)

Attempting to use an isolation level other than the default with a transaction scope would use the default isolation level. (Bug #34448)

When altering a stored procedure within Visual Studio, the parameters to the procedure could be lost. (Bug #34359)

A race condition could occur within the procedure cache resulting the cache contents overflowing beyond the configured cache size. (Bug #34338)

Using the TableAdapter wizard in combination with a suitable SELECT statement, only the associated INSERT statement would also be created, rather than the required DELETE and UPDATE statements. (Bug #31338)

Running queries based on a stored procedure would cause the data set designer to terminate. (Bug #26364)

Functionality Added or Changed

Bugs Fixed

Performing GetValue() on a field TINYINT(1) returned a BOOLEAN. While not a bug, this caused problems in software that expected an INT to be returned. A new connection string option Treat Tiny As Boolean has been added with a default value of true. If set to false the provider will treat TINYINT(1) as INT. (Bug #34052)

Some speed improvements have been implemented in the TokenizeSql process used to identify elements of SQL statements. (Bug #34220)

When accessing tables from different databases within the same TransactionScope, the same user/password combination would be used for each database connection. MySQL Connector/Net does not handle multiple connections within the same transaction scope. An error is now returned if you attempt this process, instead of using the incorrect authorization information. (Bug #34204)

The status of connections reported through the state change handler was not being updated correctly. (Bug #34082)

Incorporated some connection string cache optimizations sent to us by Maxim Mass. (Bug #34000)

In an open connection where the server had disconnected unexpectedly, the status information of the connection would not be updated properly. (Bug #33909)

MySQL Connector/Net failed to compile properly with nant. (Bug #33508)

Problem with membership provider would mean that FindUserByEmail failed with a MySqlException because it was trying to add a second parameter with the same name as the first. (Bug #33347)

Using compression in the MySQL connection with MySQL Connector/Net would be slower than using native (uncompressed) communication. (Bug #27865)

Setting the size of a string parameter after the value could cause an exception. (Bug #32094)

Creation of parameter objects with noninput direction using a constructor failed. This was cause by some old legacy code preventing their use. (Bug #32093)

A date string could be returned incorrectly by MySqlDateTime.ToString() when the date returned by MySQL was 0000-00-00 00:00:00. (Bug #32010)

A syntax error in a set of batch statements could leave the data adapter in a state that appears hung. (Bug #31930)

Installing over a failed uninstall of a previous version could result in multiple clients being registered in the machine.config. This would prevent certain aspects of the MySQL connection within Visual Studio to work properly. (Bug #31731)

MySQL Connector/Net would incorrectly report success when enlisting in a distributed transaction, although distributed transactions are not supported. (Bug #31703)

Data cached from the connection string could return invalid information because the internal routines were not using case-sensitive semantics. This lead to updated connection string options not being recognized if they were of a different case than the existing cached values. (Bug #31433)

Trying to use a connection that was not open could return an ambiguous and misleading error message. (Bug #31262)

Column name metadata was not using the character set as defined within the connection string being used. (Bug #31185)

Memory usage could increase and decrease significantly when updating or inserting a large number of rows. (Bug #31090)

Commands executed from within the state change handler would fail with a NULL exception. (Bug #30964)

Extracting data through XML functions within a query returns the data as System.Byte[]. This was due to MySQL Connector/Net incorrectly identifying BLOB fields as binary, rather than text. (Bug #30233)

When running a stored procedure multiple times on the same connection, the memory usage could increase indefinitely. (Bug #30116)

Column types with only 1-bit (such as BOOLEAN and TINYINT(1) were not returned as boolean fields. (Bug #27959)

When accessing certain statements, the command would timeout before the command completed. Because this cannot always be controlled through the individual command timeout options, a default command timeout has been added to the connection string options. (Bug #27958)

The server error code was not updated in the Data[] hash, which prevented DbProviderFactory users from accessing the server error code. (Bug #27436)

The MySqlDbType.Datetime has been replaced with MySqlDbType.DateTime. The old format has been obsoleted. (Bug #26344)

Changing the connection string of a connection to one that changes the parameter marker after the connection had been assigned to a command but before the connection is opened could cause parameters to not be found. (Bug #13991)

An incorrect ConstraintException could be raised on an INSERT when adding rows to a table with a multiple-column unique key index. (Bug #30204)

A DATE field would be updated with a date/time value, causing a MySqlDataAdapter.Update() exception. (Bug #30077)

The Saudi Hijri calendar was not supported. (Bug #29931)

Calling SHOW CREATE PROCEDURE for routines with a hyphen in the catalog name produced a syntax error. (Bug #29526)

Connecting to a MySQL server earlier than version 4.1 would raise a NullException. (Bug #29476)

The availability of a MySQL server would not be reset when using pooled connections (pooling=true). This would lead to the server being reported as unavailable, even if the server become available while the application was still running. (Bug #29409)

A FormatException error would be raised if a parameter had not been found, instead of Resources.ParameterMustBeDefined. (Bug #29312)

An exception would be thrown when using the Manage Role functionality within the web administrator to assign a role to a user. (Bug #29236)

Using the membership/role providers when validationKey or decryptionKey parameters are set to AutoGenerate, an exception would be raised when accessing the corresponding values. (Bug #29235)

Certain operations would not check the UsageAdvisor setting, causing log messages from the Usage Advisor even when it was disabled. (Bug #29124)

Using the same connection string multiple times would result in Database=dbname appearing multiple times in the resulting string. (Bug #29123)

Visual Studio Plugin: Adding a new query based on a stored procedure that uses the SELECT statement would terminate the query/TableAdapter wizard. (Bug #29098)

Using TransactionScope would cause an InvalidOperationException. (Bug #28709)

Log messages would be truncated to 300 bytes. (Bug #28706)

Creating a user failed due to the application name being set incorrectly. (Bug #28648)

Visual Studio Plugin: Adding a new query based on a stored procedure that used a UPDATE, INSERT or DELETE statement would terminate the query/TableAdapter wizard. (Bug #28536)

Visual Studio Plugin: Query Builder would fail to show TINYTEXT columns, and any columns listed after a TINYTEXT column correctly. (Bug #28437)

Accessing the results from a large query when using data compression in the connection failed to return all the data. (Bug #28204)

Visual Studio Plugin: Update commands would not be generated correctly when using the TableAdapter wizard. (Bug #26347)

Running the statement SHOW PROCESSLIST would return columns as byte arrays instead of native columns. (Bug #28448)

Installation of the MySQL Connector/Net on Windows failed if VisualStudio had not already been installed. (Bug #28260)

MySQL Connector/Net would look for the wrong table when executing User.IsRole(). (Bug #28251)

Building a connection string within a tight loop would show slow performance. (Bug #28167)

The UNSIGNED flag for parameters in a stored procedure would be ignored when using MySqlCommandBuilder to obtain the parameter information. (Bug #27679)

Using MySQLDataAdapter.FillSchema() on a stored procedure would raise an exception: Invalid attempt to access a field before calling Read(). (Bug #27668)

DATETIME fields from versions of MySQL before 4.1 would be incorrectly parsed, resulting in a exception. (Bug #23342)

Fixed password property on MySqlConnectionStringBuilder to use PasswordPropertyText attribute. This causes dots to show instead of actual password text.

Now compiles for .NET CF 2.0.

Rewrote stored procedure parsing code using a new SQL tokenizer. Really nasty procedures including nested comments are now supported.

GetSchema will now report objects relative to the currently selected database. What this means is that passing in null as a database restriction will report objects on the currently selected database only.

Added Membership and Role provider contributed by Sean Wright (thanks!).

If, when using the MySqlTransaction transaction object, an exception was thrown, the transaction object was not disposed of and the transaction was not rolled back. (Bug #39817)

Executing a command that resulted in a fatal exception did not close the connection. (Bug #37991)

When a prepared insert query is run that contains an UNSIGNED TINYINT in the parameter list, the complete query and data that should be inserted is corrupted and no error is thrown. (Bug #37968)

In a .NET application MySQL Connector/Net modifies the connection string so that it contains several occurrences of the same option with different values. This is illustrated by the example that follows.

The original connection string:

host=localhost;database=test;uid=*****;pwd=*****;
connect timeout=25; auto enlist=false;pooling=false;

The connection string after closing MySqlDataReader:

host=localhost;database=test;uid=*****;pwd=*****;
connect timeout=25;auto enlist=false;pooling=false;
Allow User Variables=True;Allow User Variables=False;
Allow User Variables=True;Allow User Variables=False;

(Bug #37955)

When creating a connection pool, specifying an invalid IP address will cause the entire application to crash, instead of providing an exception. (Bug #36432)

GetSchema did not work correctly when querying for a collection, if using a non-English locale. (Bug #35459)

When reading back a stored double or single value using the .NET provider, the value had less precision than the one stored. (Bug #33322)

The DbCommandBuilder.QuoteIdentifer method was not implemented. (Bug #35492)

Setting the size of a string parameter after the value could cause an exception. (Bug #32094)

Creation of parameter objects with noninput direction using a constructor failed. This was cause by some old legacy code preventing their use. (Bug #32093)

A date string could be returned incorrectly by MySqlDateTime.ToString() when the date returned by MySQL was 0000-00-00 00:00:00. (Bug #32010)

A syntax error in a set of batch statements could leave the data adapter in a state that appears hung. (Bug #31930)

Installing over a failed uninstall of a previous version could result in multiple clients being registered in the machine.config. This would prevent certain aspects of the MySQL connection within Visual Studio to work properly. (Bug #31731)

Data cached from the connection string could return invalid information because the internal routines were not using case-sensitive semantics. This lead to updated connection string options not being recognized if they were of a different case than the existing cached values. (Bug #31433)

Column name metadata was not using the character set as defined within the connection string being used. (Bug #31185)

Memory usage could increase and decrease significantly when updating or inserting a large number of rows. (Bug #31090)

Commands executed from within the state change handler would fail with a NULL exception. (Bug #30964)

When running a stored procedure multiple times on the same connection, the memory usage could increase indefinitely. (Bug #30116)

The server error code was not updated in the Data[] hash, which prevented DbProviderFactory users from accessing the server error code. (Bug #27436)

Changing the connection string of a connection to one that changes the parameter marker after the connection had been assigned to a command but before the connection is opened could cause parameters to not be found. (Bug #13991)

Extracting data through XML functions within a query returns the data as System.Byte[]. This was due to MySQL Connector/Net incorrectly identifying BLOB fields as binary, rather than text. (Bug #30233)

An incorrect ConstraintException could be raised on an INSERT when adding rows to a table with a multiple-column unique key index. (Bug #30204)

A DATE field would be updated with a date/time value, causing a MySqlDataAdapter.Update() exception. (Bug #30077)

Fixed bug where MySQL Connector/Net was hand building some date time patterns rather than using the patterns provided under CultureInfo. This caused problems with some calendars that do not support the same ranges as Gregorian.. (Bug #29931)

Calling SHOW CREATE PROCEDURE for routines with a hyphen in the catalog name produced a syntax error. (Bug #29526)

The availability of a MySQL server would not be reset when using pooled connections (pooling=true). This would lead to the server being reported as unavailable, even if the server become available while the application was still running. (Bug #29409)

A FormatException error would be raised if a parameter had not been found, instead of Resources.ParameterMustBeDefined. (Bug #29312)

Certain operations would not check the UsageAdvisor setting, causing log messages from the Usage Advisor even when it was disabled. (Bug #29124)

Using the same connection string multiple times would result in Database=dbname appearing multiple times in the resulting string. (Bug #29123)

Log messages would be truncated to 300 bytes. (Bug #28706)

Accessing the results from a large query when using data compression in the connection will fail to return all the data. (Bug #28204)

Fixed problem where MySqlConnection.BeginTransaction checked the drivers status var before checking if the connection was open. The result was that the driver could report an invalid condition on a previously opened connection.