Comments on: Saving without callbacks http://www.napcsweb.com/blog/2009/08/19/saving-without-callbacks/ professional web development and consulting Mon, 22 Aug 2011 18:56:36 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Brian http://www.napcsweb.com/blog/2009/08/19/saving-without-callbacks/comment-page-1/#comment-27334 Brian Thu, 27 Aug 2009 21:52:14 +0000 http://www.napcsweb.com/blog/?p=85#comment-27334 I think that's an acceptable approach, but what I don't like about it is it's not as declarative, and it's inconsistent with how update_attribute and update work. At least you know with my example by looking that I'm not triggering callbacks. Thanks for bringing that up though! I think that’s an acceptable approach, but what I don’t like about it is it’s not as declarative, and it’s inconsistent with how update_attribute and update work. At least you know with my example by looking that I’m not triggering callbacks.

Thanks for bringing that up though!

]]> By: Nick http://www.napcsweb.com/blog/2009/08/19/saving-without-callbacks/comment-page-1/#comment-27324 Nick Thu, 20 Aug 2009 06:47:15 +0000 http://www.napcsweb.com/blog/?p=85#comment-27324 What about keeping your after_save callback, but in the callback method, use update_all, which does not trigger callbacks, so you avoid the endless loop scenario. (http://api.rubyonrails.org/classes/ActiveRecord/Base.html#M002273) What about keeping your after_save callback, but in the callback method, use update_all, which does not trigger callbacks, so you avoid the endless loop scenario.

(http://api.rubyonrails.org/classes/ActiveRecord/Base.html#M002273)

]]>