duplicate association names should be rejected
Reported by Clifford Heath | September 23rd, 2010 @ 02:03 AM | in 1.1.1
If I define two different associations having the same name, DataMapper should warn and/or reject the model.
Comments and changes to this ticket
-
Martin Gamsjaeger (snusnu) January 14th, 2011 @ 07:54 PM
- State changed from “new” to “confirmed”
- Assigned user set to “Martin Gamsjaeger (snusnu)”
- Milestone set to “1.1”
- Milestone order changed from “196285” to “0”
-
Martin Gamsjaeger (snusnu) January 14th, 2011 @ 07:57 PM
Clifford,
Currently (recent master) DM overwrites the previously defined relationship. This is in line with ruby method redefinition behavior and also something I find intuitive. Do you mean that DM should warn/reject in case the
nameof the relationships match, but theirtypedoesn't? So that it's fine to redefine a, say, 1:1 relationship with the same name but different options, but not allow to create an m:1 relationship with the same name? That would make sense to me. Is this what you mean? -
Dan Kubb (dkubb) March 16th, 2011 @ 10:41 PM
- Milestone changed from “1.1” to “1.1.1”
- Milestone order changed from “16” to “0”
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 »
Clifford Heath
Martin Gamsjaeger (snusnu)
Piotr Solnica (solnic)