Save-chaining should be explicit
Reported by Sam Smoot | October 4th, 2007 @ 02:46 PM
Right now the save/validation-chaining just iterates over #instance_variables and looks for vars that respond_to :valid? and :save.
Which was just a quick hack. Instead I'd like associations to assign themselves to a model_instance#loaded_associations array on load, and we can just explicitly look at that during save.
Comments and changes to this ticket
-
Sam Smoot October 5th, 2007 @ 08:51 AM
- Milestone cleared.
-
Sam Smoot October 10th, 2007 @ 12:21 PM
loaded_associations method was added and associations assign themselves to it on instantiation.
Now the associations need #valid? and #save methods before we can modify the related commands to use the loaded_associations method.
-
-
-
-
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
- Nobody is watching this ticket.
Referenced by
-
601
[PATCH] dm-timestamps doesn't work if no fields have been set
In the future we’re going to make it so that default
valu...
-
1385
rails3 with cache_cache classes = false causes problems with many 2 many associations
Classes are auto loaded: Article (obj #1), Person (obj
#2...