This question is locked. New answers and comments are not allowed.
Hello,
We are upgrading an old intranet application using an Oracle database. We have started to use ORM to create the domain model from the existing database. There are many legacy join tables that have their own primary key field and the foreign keys of the related tables. When adding these tables to the designer, it doesn't recognise the join table as a "Join Table" and we cannot create a zero to many association between the two classes. I've tried to create the association in the designer and select a Join Table but the actual table isn't available to select.
Is there any way to create the association so that the ORM uses the join table as expected?
Many thanks,
David
We are upgrading an old intranet application using an Oracle database. We have started to use ORM to create the domain model from the existing database. There are many legacy join tables that have their own primary key field and the foreign keys of the related tables. When adding these tables to the designer, it doesn't recognise the join table as a "Join Table" and we cannot create a zero to many association between the two classes. I've tried to create the association in the designer and select a Join Table but the actual table isn't available to select.
Is there any way to create the association so that the ORM uses the join table as expected?
Many thanks,
David
3 Answers, 1 is accepted
0
Accepted
Hello David,
I already gave you the answer in the support thread on this topic but I will share it here as well, so if someone else is experiencing the same problem he could know the solution.
With the new Q3 release we have introduced a new IsJoinTable property in the MetaTable class which can be set manually and determines whether a table can be used as join table in many to many relationships. So in this case, the solution is to select the table from the Model Schema Explorer and set the IsJoinTable property to true from the Properties pane. Then the table should appear in the join table combobox of the details editor, letting you define the association correctly. Hope that helps.
Kind regards,
Alexander
the Telerik team
I already gave you the answer in the support thread on this topic but I will share it here as well, so if someone else is experiencing the same problem he could know the solution.
With the new Q3 release we have introduced a new IsJoinTable property in the MetaTable class which can be set manually and determines whether a table can be used as join table in many to many relationships. So in this case, the solution is to select the table from the Model Schema Explorer and set the IsJoinTable property to true from the Properties pane. Then the table should appear in the join table combobox of the details editor, letting you define the association correctly. Hope that helps.
Kind regards,
Alexander
the Telerik team
Do you want to have your say when we set our development plans?
Do you want to know when a feature you care about is added or when a bug fixed?
Explore the
Telerik Public Issue Tracking
system and vote to affect the priority of the items
0
Richard
Top achievements
Rank 1
Rank 1
answered on 23 Dec 2010, 05:30 PM
could you provide a link back to the support thread?
Thanks,
Rich
Thanks,
Rich
0
Hello David,
I am afraid this is not possible. The communication via support tickets is confidential and not publicly available. However, if you are experiencing any problems with our product, please do let us know and we will try to help you the best way we can.
Greetings,
Alexander
the Telerik team
I am afraid this is not possible. The communication via support tickets is confidential and not publicly available. However, if you are experiencing any problems with our product, please do let us know and we will try to help you the best way we can.
Greetings,
Alexander
the Telerik team