okey doke -- thanks for the confirmation. On Aug 31, 5:04 am, Chris Mear <[email protected]> wrote: > On 30 August 2010 17:39, richardsugg <[email protected]> wrote: > > > > > > > > > > > First - in the subject I said "after_save" but meant "after_create" > > but the issue is the same. I think I may have just figured it out, > > but perhaps you could verify. I have a project model and events > > models. When I create a project, I loop through an array that creates > > default events. I noticed that all the events were getting created > > twice. Here's the Project model: > > > class Project < ActiveRecord::Base > > has_many :events > > after_create :after_create > > > def after_create > > ## create my default events > > end > > end > > > The problem, I think, is that after_create is called automatically, > > and you only need to have the "after_create :after_create" line if the > > callback is named something besides callback event. Once I took out > > the "after_create :after_create" line, it seemed to work. I didn't > > try it, but I suppose I could have left it in but named the method > > something besides "after_create" like "add_default_events." > > > So is what I have said correct? > > Yes, that's correct. It was being called twice because you had defined > the 'after_create' method, which gets called automatically, *and* you > had added your 'after_create' method to the after_create callback > chain by calling 'after_create :after_create'. > > Chris
-- 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 [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
