[dm-constraints] should default to :constraint => :protect
Reported by Martin Gamsjaeger (snusnu) | April 25th, 2009 @ 12:18 PM | in 0.10.0
Hey,
dm-constraints shouldn't bail out if it is loaded and the :constraint option is not specified. I was talking to dkubb yesterday and he said that the desired behavior would be to assume :constraint => :protect to be the default.
You can find the error I get at http://pastie.org/457827 . The workaround is to add a :constraint option to every single association (which is probably a good idea anyway), but there should be a sensible default.
cheers snusnu
Comments and changes to this ticket
-
Dan Kubb (dkubb) June 16th, 2009 @ 04:43 PM
- Assigned user changed from “Balint Erdi” to “Dan Kubb (dkubb)”
- State changed from “unconfirmed” to “resolved”
- Milestone set to “0.10.0”
dm-constraints in dm-more/next has specs in place to ensure the :constraint option is not required. And yes, the default if you don't specify anything is the same as if you passed in :constraint => :protect.
I am marking this as resolved but please confirm in your local app that it is working for you.
-
-
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 »
People watching this ticket
Balint Erdi
Dan Kubb (dkubb)
Martin Gamsjaeger (snusnu)
Tags
Referenced by
-
864
auto_migrate! blows up on mysql if dm-constraints are enabled
This is related to #839 and is resolved.