#1313 ✓resolved
Jonathan Stott (namelessjon)

DataMapper.finalize can incorrectly declare a model invalid

Reported by Jonathan Stott (namelessjon) | June 10th, 2010 @ 06:11 AM

When creating an explicitly named join model, it is now possible to declare multiple belongs_to :parent, :key => true entries. Depending on the require order, it is possible that the join model will be required (and thus appear in the descendant set) before either of the parents. In this case the check for a key will fail, as none of the belongs_to relationships are initialized

This is fixed in:


Comments and changes to this ticket

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.

New-ticket Create new ticket

Create your profile

Help contribute to this project by taking a few moments to create your personal profile. Create your profile »


Referenced by