:constraint option interferes even when dm-constraints are not loaded
Reported by Martin Gamsjaeger (snusnu) | August 18th, 2009 @ 12:59 PM | in 0.10.0
standalone script showing the error can be found at http://pastie.org/585069
Comments and changes to this ticket
-
Martin Gamsjaeger (snusnu) August 23rd, 2009 @ 10:51 PM
- Tag changed from “dm-constraints” to “dm-constraints, regression”
- State changed from “unconfirmed” to “confirmed”
Marked it as a regression because I'm pretty sure that this was already working in the next series.
-
Dan Kubb (dkubb) September 2nd, 2009 @ 11:57 AM
- Tag changed from “dm-constraints, regression” to “dm-constraints”
- State changed from “confirmed” to “not-applicable”
If dm-constraints is not loaded, the :constraint option will be treated by DataMapper as a condition to apply when the relationship is queried. The fact that it is exploding isn't surprising, every non-reserved option provided in the Relationship declaration is assumed to be a condition on the query. Adding "require 'dm-constraints'" resolves the issue.
Marking this ticket as not-applicable.
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)
Martin Gamsjaeger (snusnu)