On Aug 21, 5:47 pm, IAmNan <dger...@gmail.com> wrote:
> So, if there are limitations on what you can do in a callback filter, > we should probably documented it somewhere. However, I might even > call it a bug. What do you think? > Doesn't sound like anything to do with callbacks to me. I think the root of the problem is that there are multiple instances of parent in memory - the one you created explicitly, and the ones loaded from the database when you call parent from the child object. Although they refer to the same row in the database, they are distinct in memory objects (if you inspect the value of parent it should change). There's a plugin (parental_control) that goes someway to fixing this by adding an :inverse_of option to associations which I believe was merged into trunk (not in rails 2.3.x if my memory is correct) Fred -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-t...@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-talk+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
