You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 17, 2018. It is now read-only.
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 name of the relationships match, but their type doesn’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?
If I define two different associations having the same name, DataMapper should warn and/or reject the model.
Created by Clifford Heath - 2010-09-23 07:03:10 UTC
Original Lighthouse ticket: http://datamapper.lighthouseapp.com/projects/20609/tickets/1417
The text was updated successfully, but these errors were encountered: