Normally (I assume) when you use the many2many relationship the ORM creates a junction table for you and the order in which the records are returned for either direction is the order in which they were created/populated the database.
I have a situation where I have two entities:
The same sequence can be associated with more than one procedure, however each procedure has a unique sort order.
For instance procedure A, B, C may reference dozens of Sequences, but all share Sequence B, however Sequence B may be the first sequence on Procedure A, the second last on Procedure B, etc...
Would I solve this problem by simply introducing the junction table explicitly in the model - using double one to one relationships?
Please try to give a substantial answer. If you wanted to comment on the question or answer, just use the commenting tool. Please remember that you can always revise your answers - no need to answer the same question twice. Also, please don't forget to vote - it really helps to select the best questions and answers!
About This Community
|Asked: 5/21/15, 9:21 AM|
|Seen: 603 times|
|Last updated: 6/11/15, 9:07 AM|