Bug #62062 Foreign Key Errors
Submitted: 2 Aug 2011 20:24 Modified: 4 Sep 2011 7:13
Reporter: Daniel Olunaike Email Updates:
Status: No Feedback Impact on me:
None 
Category:Connector / NET Severity:S2 (Serious)
Version:6.4.3 OS:Microsoft Windows
Assigned to: Bogdan Degtyariov CPU Architecture:Any

[2 Aug 2011 20:24] Daniel Olunaike
Description:
Hi,

I am using MySQL 5.5, Connector .Net 6.4.3 and VS 2010 Pro.

1. I found out while generating Entity Data Model in EF that one-to-one, one-to-many, relationships are translated to zero-or-one relationship in EF Designer. This actually is a carried over bug from v6.3.6 which I migrated from.

2. I also found out that the Foreign Key bug in editing or creating a new table in VS 2010 is "partially" fixed as a new new error is being displayed saying "Unable to save object with error: Can't create table... (errno: 150).

Thank you. 

How to repeat:
1. Generate an EDM from an existing MySQL database with foreign key constraints.

2. Edit or create a new table and add relationship.

N.B. I also suspect this to be a bug. If you try to edit a child table (ie. A table that has the many side of the relationship) in VS 2010 you get an error saying "Object reference not set to an instance of an object". This also is carried over from v6.3.6.
[4 Aug 2011 7:13] Bogdan Degtyariov
Hi Daniel,

Can you please clarify what you mean when saying about "carried over bug from 6.3.6"? Does it mean that the Entity Data Model was actually generated using Connector/NET 6.3.6, but the new version 6.4.3 fails with this model?

Or 6.4.3 makes the same incorrect relationship when you create a new model from the database?
[4 Sep 2011 23:00] Bugs System
No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".