has 1 requires plural model name
Reported by Mikoangelo | December 14th, 2008 @ 09:21 PM
When specifying a has-one relation, passing a singular model name causes it to be unnecessarily singularized. The docs agree.
Associations#has should not singularize the model name when cardinality is 1.
Comments and changes to this ticket
-
Mikoangelo December 14th, 2008 @ 10:44 PM
Upon later investigations it turns out that it actually stores that symbol as the name of the child. Parent has one Kid, you go
has 1, :kidsout of necessity, and it'll beParent.first.kids # => #<Kid: …>. -
Mikoangelo December 15th, 2008 @ 12:38 AM
It's possible to work around it by manually specifying the class_name, it turns out. This also changes the relevant methods.
-
Dan Kubb (dkubb) January 8th, 2009 @ 05:16 AM
- State changed from “unconfirmed” to “accepted”
- Assigned user set to “Dan Kubb (dkubb)”
-
Jonathan Stott (namelessjon) February 22nd, 2009 @ 09:23 AM
- State changed from “accepted” to “resolved”
Resolved in 0.10.0
See #554
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
Mikoangelo