Ar Chron wrote: > Juan Kinunt wrote: >> I would use after_create inside the Company model but I need to populate >> a lot of data and I think the model is not a good place. > > Why is that? It certainly sounds like your creation of a company > requires the writing of some additional data, which are effectively > default attributes of a company, no?
For example, a Company has_many Threats and a Threat belongs_to a Company and I want to populate the table Threats with some default threats when a Company is created. I don't use the same threats for each company because each company can add, delete and modify their threats as they want, so I don't want to share threats. If you think this can be done differently better any hint will be really appreciated :) -- Posted via http://www.ruby-forum.com/. -- 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.
