New "bug" since last update

[Zero-G.]

Hey

I have found a new "bug" in your latest update.
When I choose OneToOne Relation between two tables, than in both direction, a 1:1 relation is build. - In older versions, it was a real ManyToOne Relation.
Now, I get errors, when other 3rd Party software do check all Relations.

Because in real, I do have Many to One relations and no real One to One relations.
Please tell me, what you will do with this in future, will there be a ManyToOne relation in EF Designer? - Or can you please check it this way, that it will get compatible to older versions.

THX

[MariiaI]

Sorry for the delay. Please specify the following:
1) whether you are working with LinqConnect or Entity Framework ORM (as you mentioned EF Designer in your post);
2) what relationships exactly do you mean: do you choose OneToOne Relation between two tables in the database, or in the model?

Please specify detailed steps to reproduce this behavior.

[Zero-G.]

Hey

I am working with EF Designer - Not LinqConnect (sorry for that)

do you choose OneToOne Relation between two tables in the database, or in the model

The OneToOne Relation is set in the model (mySQL doesn't allow this specification - so, in the database, there is a ForeignRelation set between the two tables)

THX

[Shalex]

Please send us a test model and tell us the steps we should follow to reproduce an incorrect behaviour (also specify the behaviour which you consider as a correct one).

[Zero-G.]

Hey

I found the Problem by my self. - Sorry, THX