On Mon, Jun 27, 2011 at 9:37 AM, Peter Bell <[email protected]> wrote: > I'm specifically looking to ensure that nobody on the team will write > "user.teachers << teacher" and bypass all of the additional business > logic in the add_teacher method.
Maybe you could instead just use the Association callbacks -- before_add, after_add, before_remove, after_remove to run your business logic on each operation? FWIW, -- Hassan Schroeder ------------------------ [email protected] http://about.me/hassanschroeder twitter: @hassan -- 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.
