Association was ignored, can you help me
-
- Posts: 13
- Joined: Sun 15 Aug 2010 11:08
Association was ignored, can you help me
Please i have a problem: i have oracle database with a small set of tables and foreign keys between each other, when i generate the model from the database using entity framework designer most of this foreign keys didn't mapped but when i use EntityDeveloper every thing is OK, Can you help me to know why this was happen
-
- Devart Team
- Posts: 1710
- Joined: Thu 03 Dec 2009 10:48
Sorry for the delay.
Could you please specify or send us the definitions of the tables used? We couldn't reproduce the problem with our test databases.
Also, please specify the versions of dotConnect for Oracle and Oracle server you are using.
Could you please specify or send us the definitions of the tables used? We couldn't reproduce the problem with our test databases.
Also, please specify the versions of dotConnect for Oracle and Oracle server you are using.
-
- Posts: 13
- Joined: Sun 15 Aug 2010 11:08
-
- Devart Team
- Posts: 1710
- Joined: Thu 03 Dec 2009 10:48
-
- Devart Team
- Posts: 1710
- Joined: Thu 03 Dec 2009 10:48
-
- Posts: 13
- Joined: Sun 15 Aug 2010 11:08
Wait your answer
OK thanks, but pleas i wait your answer
-
- Posts: 13
- Joined: Sun 15 Aug 2010 11:08
Any answers ?
Is there are any answers ?
-
- Posts: 13
- Joined: Sun 15 Aug 2010 11:08
Any answers ?
Is there are any answers ?
-
- Posts: 13
- Joined: Sun 15 Aug 2010 11:08
Any answers ?
Is there are any answers ?
-
- Devart Team
- Posts: 1710
- Joined: Thu 03 Dec 2009 10:48
-
- Devart Team
- Posts: 1710
- Joined: Thu 03 Dec 2009 10:48
Thank you for your assistance, there were two issues with generating the model:
1) The foreign keys missed in the EDM wizard. The problem is that the EDM wizard behaviour depends on the order in which foreign keys are retrieved. This can cause such issues in the case when a table has multiple associations. We've fixed the issue, the fix will be available in the nearest build.
2) Incorrect associations in Entity Developer. This issue is caused by incorrectly formed primary key (e.g., for the L_FDOC table). We will inform you when this problem is fixed.
1) The foreign keys missed in the EDM wizard. The problem is that the EDM wizard behaviour depends on the order in which foreign keys are retrieved. This can cause such issues in the case when a table has multiple associations. We've fixed the issue, the fix will be available in the nearest build.
2) Incorrect associations in Entity Developer. This issue is caused by incorrectly formed primary key (e.g., for the L_FDOC table). We will inform you when this problem is fixed.