Bug #79153 Connectors from 6.7.4: incorrect schema connecting to previous web aps on 5.6.24
Submitted: 6 Nov 2015 12:00 Modified: 26 Nov 2015 12:49
Reporter: André Morais Email Updates:
Status: Can't repeat Impact on me:
Category:Connector / NET Severity:S2 (Serious)
Version:6.9.8 OS:Windows
Assigned to: CPU Architecture:Any
Tags: Incorrect schema

[6 Nov 2015 12:00] André Morais
.Net web application connecting to MySQL Server 5.6.24 (community edition) was working fine with connector for .Net 6.6.4. 
After updating the connector it always returns "incorrect schema". Tried several others: 6.7.4, 6.9.7, 6.9.8. 
Connecting to another later server (5.6.27) with these connectors works fine.
Documentation says these connectors are compatible with servers 5.5, 5.6 and 5.7.

How to repeat:
Create dummy .net web application with MySQLProvider of type "MySql.Web.Security.MySQLMembershipProvider" and "autogenerateschema"="true" using connector 6.6.4 on a 5.6.24 server. 
Open application and check if tables were created.
Change reference to connector 6.9.8 and try opening the application.

Suggested fix:
Has to be debugged to determine the problem.
[12 Nov 2015 13:15] Chiranjeevi Battula
Hello André Morais,

Thank you for the bug report.
I tried to reproduce the issue at my end using Visual Studio 2013 (C#.Net), MySQL Connector/Net 6.9.8 but not seeing any issue in schema selection.
Could you please list out exact steps you tried out at your end, this would help us to reproduce the issue at our end.

[12 Nov 2015 14:59] André Morais
Hello Chiranjeevi,

   As I said, the problem only occurs when a schema was created with an old version of the connector, such as the 6.6.4, on a 5.6.24 server. When I upgrade the MySQL Connector to 6.9.8 and try to open the application I get an error.

   I am using VS 2012 (C#.Net). Created the web application with C# 4.0 and using "autogenerateschema=true" using the MySQL Connector .Net 6.6.4 and set a connection string to a 5.6.24 community edition server. Changed the connector to 6.9.8 version.

   The schema is not corrupted, however, since changing it back restores functionality.

    Thanks for your help,

             André Morais
[26 Nov 2015 12:49] Chiranjeevi Battula
Hello   André Morais,

Thank you for your feedback.
I could not repeat the issue on Visual Studio 2013 (C#.Net) with  MySQL 5.6.24 and 5.6.27 and Connector/Net  6.6.4, 6.9.7 and 6.9.8 versions.
If you can provide more information, feel free to add it to this bug and change the status back to 'Open'.

Thank you for your interest in MySQL.