This is a migrated thread and some comments may be shown as answers.

Model-first approach. Using Default Join Table - Changes will not migrate.

1 Answer 22 Views
Development (API, general questions)
This is a migrated thread and some comments may be shown as answers.
This question is locked. New answers and comments are not allowed.
Hunter
Top achievements
Rank 1
Hunter asked on 01 Aug 2013, 05:05 AM

I am trying to use the following approach to create a Default Many-To-Many relationship and then migrate the changes to my DB
Using Default Join Table

I see the relationship line showing many-to-many *----------*. I right click and choose Update Database from Model...
I do not see the pending changes. Am I missing something?

Please note that I have already previously created the database for the first time based on my domain model. I am currently trying to migrate the many-to-many changes.


Also, could someone please explain why this default join table is useful? Isn't it much cleaner to have full control and manually create the join table in every situation like in this approach? 
Using Custom Join Table

1 Answer, 1 is accepted

Sort by
0
Accepted
Kristian Nikolov
Telerik team
answered on 02 Aug 2013, 01:40 PM
Hi Hunter,

I have reviewed your problem and you are not missing anything, this is the expected behavior of Telerik OpenAccess ORM. For consistency, I have posted my full answer in your other thread.

In case the provided information is insufficient, do not hesitate to get back to us.

Regards,
Kristian Nikolov
Telerik
OpenAccess ORM Q2 2013 brings you a more powerful code generation and a unique Bulk Operations support with LINQ syntax. Check out the list of new functionality and improvements shipped with this release.
Tags
Development (API, general questions)
Asked by
Hunter
Top achievements
Rank 1
Answers by
Kristian Nikolov
Telerik team
Share this question
or