What is covered by save(:validate => false)?

Question

I just implemented a number of custom counter_caches using code like this:

def after_save
    self.update_counter_cache
end
def after_destroy
    self.update_counter_cache
end
def update_counter_cache
    self.company.new_matchings_count = Matching.where(:read => false).count
    self.company.save
end

My question is this - what does the command Model.save(:validate => false) actually prevent beyond things like validates_with or before_validation?

Will my custom counter_caches be affected if I keep my existing saves without validation?

score 4 · Answer 1 · answered Jan 17 '17 at 06:53

4

Testing on Rails 4.2.6 shows that .save(:validate=>false) will actually skip before_validations and after_validation callbacks.

answered Jan 17 '17 at 06:53

lulalala

16,796
13
106
167

score 3 · Accepted Answer · answered Mar 18 '11 at 18:20

3

If you pass in the :validate=>false, it skips the valid? command. Everything else functions the same.

You can check the code out here: http://api.rubyonrails.org/classes/ActiveRecord/Validations.html

def save(options={})
  perform_validations(options) ? super : false
end

...

if perform_validation
  valid?(options.is_a?(Hash) ? options[:context] : nil)
else
  true
end

answered Mar 18 '11 at 18:20

Jesse Wolgamott

40,057
4
80
107

how do you pass in :validate => false? I tried false do |f| %> and it broke everything. I'm a bit of a newbie... – Leahcim Dec 03 '11 at 16:57
@Michael that's in the update/create method of your controller... `@model.save(:validate=>false)` – Jesse Wolgamott Dec 03 '11 at 18:13

What is covered by save(:validate => false)?

2 Answers2

Linked