Thanks. And thanks for the heads up about "Request". I'm a teacher, and my first rails project was something to organize lists of students, and the very first thing I did was to create a model named "Class". You can probably imagine where that got me.
Mark On Nov 14, 2010, at 4:09 PM, Matt Jones wrote: > I'm not sure the lifecycle mechanism can explicitly handle this, as it's > mostly focused on things occurring within the context of a single model. > Typically, one would model this with auto_actions_for and callbacks. > > in RecipeController: > > auto_actions_for :request, [:new, :create] > > and have Recipe belongs_to :request > > One important note: naming a model Request is going to cause "interesting" > things to happen in the controller, as @request is already used (at least in > Rails 2.3). It might be a good idea to name the model more specifically... > > --Matt Jones -- You received this message because you are subscribed to the Google Groups "Hobo Users" 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/hobousers?hl=en.
