Relations fail to resolve correctly with multiple repositories
Reported by Mikoangelo | December 16th, 2008 @ 06:32 PM
When trying to access a child's parent (1:N relationship), and both have been defined a non-default repository, the model will look in the default repository. The attached test case (also available at http://gist.github.com/36859) illustrates the error.
Comments and changes to this ticket
-
Dan Kubb (dkubb) December 17th, 2008 @ 08:47 PM
- State changed from “unconfirmed” to “confirmed”
I think the solution to this will be to create the concept of relative and absolute repositories for relationships.
The idea being that if you don't specify the end-point repository of a relationship, the current resource's repository should be used. Otherwise if you specify the relationship repository it will always be used regardless of what the current resources' repository is.
-
Dan Kubb (dkubb) January 8th, 2009 @ 04:51 AM
- State changed from “confirmed” to “accepted”
- Assigned user set to “Dan Kubb (dkubb)”
-
Jonathan Stott (namelessjon) February 22nd, 2009 @ 03:12 PM
- Tag set to “has_n, one_file_test, repository”
This problem still persists as of 02a93b11ce576361789340f78babf7bd4f796161, as shown in the attached test (updated for 0.10.0)
-
Dan Kubb (dkubb) May 28th, 2009 @ 04:46 AM
- State changed from “accepted” to “resolved”
This appears to have been resolved in the dm-core/next branch. Attached is script (Jonathan's with a small modification) that verifies the intended behavior.
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create new ticket
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile »
Dan Kubb (dkubb)
Lin Jen-Shin