7

Possible Duplicate:
How can I avoid running ActiveRecord callbacks?

In rails 2 there was a private method on active_records called create_without_callbacks which you could call to save a record into the database without triggering the callbacks associated with that object. This method has disappeared in rails 3, is there any way to achieve the same thing?

Community
  • 1
  • 1
opsb
  • 29,325
  • 19
  • 89
  • 99
  • 1
    This question explicitly states Rails 3. The supposed duplicate was written back in Rails 2 days, now contains rails 4 info, but doesn't specifically address creating records in Rails 3 (although it does contain information on updating existing records in Rails 3). This question is separate and distinct and not a duplicate in my opinion. – IAmNaN Apr 14 '13 at 19:56

4 Answers4

2

You are preventing certain business logic from happening when you'd call create_without_callbacks. Consider removing the callbacks if they are not needed, or use the :if and :unless options to trigger the callback only when needed.

Ariejan
  • 10,910
  • 6
  • 43
  • 40
  • When I'm unit testing an object that depends on another I often want to mock out the dependency. Unfortunately, if I do that active_record complains that the mock isn't of the correct type. In rails 2 I got around this by using factory girl to create what were effectively stubs of the correct type. I added a factory girl strategy that inserted a record using the create_without_callbacks method as they were irrelevant. – opsb Oct 25 '10 at 13:42
  • 1
    I understand, but that way you wouldn't be testing agains 'real life' objects. So, essentially you are not testing your application code. I always use Blueprint or FactoryGirl to create valid objects, including callbacks. – Ariejan Oct 25 '10 at 13:51
  • I use cucumber to do integration testing. When I'm unit testing the only 'real' object that I care about is the one I'm testing. – opsb Oct 25 '10 at 15:15
0

I don't know if all of this still work in R3, at least in 2.3.8 they did.

if it is just one attribute then

self.update_attribute(:attribute, value)

If it is multiple attributes on one object

self.update_attributes({:attribute => value})

You can also update all records with some conditions

update_all( "category = 'authorized' approved = 1, author = 'David'" )

The last one I just took from the rails API, I think it doesn't invoke callbacks but I'm not for sure on that.

thenengah
  • 42,557
  • 33
  • 113
  • 157
  • You cannot call `update_attributes` on an unsaved object. The goal is to create a new object without calling the callbacks. – Ariejan Oct 25 '10 at 13:41
  • 1
    yeah, I didn't see the create in the questions. – thenengah Oct 25 '10 at 18:12
  • 1
    By the way, update_attribute does not run validations. It does run callbacks. Update attributes essentialy is just shorthand for foo.attributes = hsh; foo.save – TheDeadSerious Sep 29 '11 at 15:42
0

Having looked at the source for rails3 it seems callbacks are added in such a way that the model.save method doesn't actually know about them.

The solution I've gone for is to mock out Model.find and return an instance that hasn't been saved. This is actually how unit tests should be done and they run faster to boot.

If you are interested in finding a hack I suggest you look at

  • rails3/activesupport/lib/active_support/callbacks.rb
  • rails3/activemodel/lib/active_model/callbacks.rb
  • rails/activerecord/lib/active_record/callbacks.rb

in that order.

opsb
  • 29,325
  • 19
  • 89
  • 99
0

You can use sneaky-save gem: https://rubygems.org/gems/sneaky-save

Zinin Serge
  • 19
  • 1