How can I avoid running ActiveRecord callbacks

Question

I have some models that have after save callbacks  Usually that s fine  but in some situations  like when creating development data  I want to save the models without having the callbacks run  Is there a simple way to do that  Something akin to     Person save   run callbacks   gt  false     or  Person save without callbacks   I looked in the Rails docs and didn t find anything  However in my experience the Rails docs don t always tell the whole story   UPDATE  I found a blog post that explains how you can remove callbacks from a model like this   Foo after save clear   I couldn t find where that method is documented but it seems to work

User · Answer

You could try something like this in your Person model:

after_save :something_cool, :unless => :skip_callbacks

def skip_callbacks
  ENV[RAILS_ENV] == 'development' # or something more complicated
end

EDIT: after_save is not a symbol, but that's at least the 1,000th time I've tried to make it one.

User · Answer

A solution that should work across all versions of Rails without the use of a gem or plugin is simply to issue update statements directly  eg  ActiveRecord  Base connection execute  update table set foo   bar where id     self id     This may  or may not  be an option depending on how complex your update is  This works well for eg updating flags on a record from within an after save callback  without retriggering the callback

User · Answer

Not the cleanest way  but you could wrap the callback code in a condition that checks the Rails environment   if Rails env     production

User · Answer

Looks like one way to handle this in Rails 2 3  since update without callbacks is gone  etc    would be to use update all  which is one of the methods that skips callbacks as per section 12 of the Rails Guide to validations and callbacks   Also  note that if you are doing something in your after  callback  that does a calculation based on many association  i e  a has many assoc  where you also do accepts nested attributes for   you will need to reload the association  in case as part of the save  one of its members was deleted

User · Answer

If you are using Rails 2  You could use SQL query for updating your column without running callbacks and validations   YourModel connection execute  UPDATE your models SET your models column name   value  WHERE your models id   ym id      I think it should work in any rails versions

User · Answer

The most up-voted answer might seem confusing in some cases    You can use just a simple if check if you would like to skip a callback  like this   after save  set title  if  - gt     new record   amp  amp  self name changed

User · Answer

I needed a solution for Rails 4  so I came up with this   app models concerns save without callbacks rb  module SaveWithoutCallbacks    def self included base      base const set  WithoutCallbacks        Class new ActiveRecord  Base  do         self table name   base table name       end           end    def save without callbacks     new record    create without callbacks   update without callbacks   end    def create without callbacks     plain model   self class const get  WithoutCallbacks      plain record   plain model create self attributes      self id   plain record id     self created at   Time zone now     self updated at   Time zone now      new record   false     true   end    def update without callbacks     update attributes   attributes except self class primary key      update attributes  created at     Time zone now     update attributes  updated at     Time zone now     update columns update attributes   end  end   in any model   include SaveWithoutCallbacks   then you can   record save without callbacks   or  Model  WithoutCallbacks create attributes

User · Answer

rails 3     MyModel send     symbol  callbacks     list   MyModel reset callbacks symbol   reset

User · Answer

Something that should work with all versions of ActiveRecord without depending on options or activerecord methods that may or may not exist   module PlainModel   def self included base      plainclass   Class new ActiveRecord  Base  do       self table name   base table name     end     base const set  Plain  plainclass    end end     usage class User  lt  ActiveRecord  Base   include PlainModel    validates presence of  email end  User create email               fail due to validation User  Plain create email        success  no validation  no callbacks  user   User  Plain find 1  user email      user save   TLDR  use a  different activerecord model  over the same table

User · Answer

This solution is Rails 2 only   I just investigated this and I think I have a solution  There are two ActiveRecord private methods that you can use   update without callbacks create without callbacks   You re going to have to use send to call these methods  examples   p   Person new  name   gt   foo   p send  create without callbacks   p   Person find 1  p send  update without callbacks    This is definitely something that you ll only really want to use in the console or while doing some random tests  Hope this helps

User · Answer

When I need full control over the callback  I create another attribute that is used as a switch  Simple and effective   Model   class MyModel  lt  ActiveRecord  Base   before save  do stuff  unless   skip do stuff callback   attr accessor  skip do stuff callback    def do stuff     puts  do stuff callback    end end   Test   m   MyModel new      Fire callbacks m save    Without firing callbacks m skip do stuff callback   true m save    Fire callbacks again m skip do stuff callback   false m save

User · Answer

for rails 3   if  ActiveRecord  Base private method defined   update without callbacks     def update without callbacks       attributes with values   arel attributes values false  false  attribute names        return false if attributes with values empty        self class unscoped where self class arel table self class primary key  eq id   arel update attributes with values      end   end

User · Answer

If the goal is to simply insert a record without callbacks or validations  and you would like to do it without resorting to additional gems  adding conditional checks  using RAW SQL  or futzing with your exiting code in any way  consider using a  shadow object  pointing to your existing db table  Like so   class ImportedPerson  lt  ActiveRecord  Base   self table name    people  end   This works with every version of Rails  is threadsafe  and completely eliminates all validations and callbacks with no modifications to your existing code  You can just toss that class declaration in right before your actual import  and you should be good to go  Just remember to use your new class to insert the object  like   ImportedPerson new  person attributes

User · Answer

You can use update columns   User first update columns   name   gt   sebastian    age   gt  25        Updates the given attributes of an object  without calling save  hence skipping validations and callbacks

User · Answer

You can use sneaky-save gem  https   rubygems org gems sneaky-save   Note this cannot help in saving associations along without validations  It throws error  created at cannot be null  as it directly inserts the sql query unlike a model  To implement this  we need to update all auto generated columns of db

User · Answer

The only way to prevent all after save callbacks is to have the first one return false   Perhaps you could try something like  untested    class MyModel  lt  ActiveRecord  Base   attr accessor  skip after save    def after save     return false if  skip after save         blah blah       end end       m   MyModel new       etc etc m skip after save   true m save

User · Answer

For creating test data in Rails you use this hack   record   Something new attrs  ActiveRecord  Persistence instance method  create record  bind record  call   https   coderwall com p y3yp2q edit

User · Answer

None of these points to without callbacks plugin that just does what you need      class MyModel  lt  ActiveRecord  Base   before save  do something before save    def after save     raise RuntimeError   after save called    end    def do something before save     raise RuntimeError   do something before save called    end end  o   MyModel new MyModel without callbacks  before save   after save  do   o save   no exceptions raised end   http   github com cjbottaro without callbacks works with Rails 2 x

User · Answer

I wrote a plugin that implements update without callbacks in Rails 3   http   github com dball skip activerecord callbacks  The right solution  I think  is to rewrite your models to avoid callbacks in the first place  but if that s impractical in the near term  this plugin may help

User · Answer

Use update column  Rails  gt   v3 1  or update columns  Rails  gt   4 0  to skip callbacks and validations  Also with these methods  updated at is not updated   Rails  gt   v3 1 only  person update column  some attribute   value    Rails  gt   v4 0 only  person update columns attributes   http   api rubyonrails org classes ActiveRecord Persistence html method-i-update column  2  Skipping callbacks that also works while creating an object class Person  lt  ActiveRecord  Base   attr accessor  skip some callbacks    before validation  do something   after validation  do something else    skip callback  validation   before   do something  if   skip some callbacks   skip callback  validation   after   do something else  if   skip some callbacks end  person   Person new person params  person skip some callbacks   true person save  UPDATE  2020  Apparently Rails has always supported  if and  unless options  so above code can be simplified as  class Person  lt  ActiveRecord  Base   attr accessor  skip some callbacks    before validation  do something  unless   skip some callbacks   after validation  do something else  unless   skip some callbacks end  person   Person new person params  person skip some callbacks   true person save

User · Answer

For custom callbacks  use an attr accessor and an unless in the callback   Define your model as follows   class Person  lt  lt  ActiveRecord  Base    attr accessor  skip after save callbacks    after save  do something  unless   skip after save callbacks  end   And then if you need to save the record without hitting the after save callbacks you defined  set the skip after save callbacks virtual attribute to true   person skip after save callbacks    gt  nil person save   By default  this  will  call  do something  after saving   person skip after save callbacks   true person save   This  will not  call  do something  after saving   person skip after save callbacks   nil   Always good to return this value back to its default so you don t accidentally skip callbacks

User · Answer

I faced the same problem when I wanted to run a Rake Task but without running the callbacks for every record I was saving  This worked for me  Rails 5   and it must work for almost every version of Rails  class MyModel  lt  ApplicationRecord   attr accessor  skip callbacks   before create  callback1   before update  callback2   before destroy  callback3    private   def callback1     return true if  skip callbacks     puts  quot Runs callback1 quot        Your code   end   def callback2     return true if  skip callbacks     puts  quot Runs callback2 quot        Your code   end     Same for callback3 and so on     end  The way it works is that it just returns true in the first line of the method it skip callbacks is true  so it doesn t run the rest of the code in the method  To skip callbacks you just need to set skip callbacks to true before saving  creating  destroying  rec   MyModel new     Or Mymodel find   rec skip callbacks   true rec save

User · Answer

Why would you want to be able to do this in development  Surely this will mean you are building your application with invalid data and as such it will behave strangely and not as you expect in production   If you want to populate your dev db with data a better approach would be to build a rake task that used the faker gem to build valid data and import it into the db creating as many or few records as you desire  but if you are heel bent on it and have a good reason I guess that update without callbacks and create without callbacks will work fine  but when you are trying to bend rails to your will  ask yourself you have a good reason and if what you are doing is really a good idea

User · Answer

https   gist github com 576546  just dump this monkey-patch into config initializers skip callbacks rb  then   Project skip callbacks    project save     or the like   all credit to the author

User · Answer

Updated     Vikrant Chaudhary s solution seems better     Rails  gt   v3 1 only  person update column  some attribute   value    Rails  gt   v4 0 only  person update columns attributes      My original answer    see this link   How to skip ActiveRecord callbacks   in Rails3    assume we have a class definition    class User  lt  ActiveRecord  Base   after save  generate nick name end    Approach1    User send  create without callbacks  User send  update without callbacks    Approach2   When you want to skip them in your rspec files or whatever  try this    User skip callback  save   after   generate nick name  User create      NOTE  once this is done  if you are not in rspec environment  you should reset the callbacks   User set callback  save   after   generate nick name    works fine for me on rails 3 0 5

User · Answer

Another way would be to use validation hooks instead of callbacks  For example    class Person  lt  ActiveRecord  Base   validate on create  do something   def do something      something clever goes here    end end   That way you can get the do something by default  but you can easily override it with     person   Person new  person save false

User · Answer

One option is to have a separate model for such manipulations  using the same table   class NoCallbacksModel  lt  ActiveRecord  Base   set table name  table name of model that has callbacks     include CommonModelMethods   if there are          end    Same approach might make things easier for bypassing validations   Stephan

[ruby-on-rails] How can I avoid running ActiveRecord callbacks?

Examples related to ruby-on-rails

Examples related to ruby

Examples related to rails-activerecord