Rails 4:after_update回调导致无限循环 [英] Rails 4: after_update callback leads to endless loop
本文介绍了Rails 4:after_update回调导致无限循环的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!
问题描述
我在我的用户模型中使用after_update回调。
Model User.rb
$ b b
after_update:check_phone
check_phone
phone_validation如果phone_changed?
end
def phone_validation
code = Array.new(8){rand(36).to_s(36)}。join
self.phone_verification_code = code
self.save
end
然而,这导致了无限循环。问题是,在phone_validation方法中 self.save
后再次调用回调。 phone_changed?
显然仍然会返回 true
。如何更改此行为?
解决方案
User.rb
attr_accessor:phone_checked
after_update:check_phone, unless => phone_checked
check_phone
phone_validation如果phone_changed?
end
def phone_validation
code = Array.new(8){rand(36).to_s(36)}。join
self.phone_verification_code = code
self.phone_checked = true#update flag
self.save
end
或
谨慎使用: skip callbacks
def phone_validation
code = Array.new(8){rand(36).to_s(36)}。join
self.update_column(:phone_verification_code => code)
end
I use the after_update callback in my User model.
Model User.rb
after_update :check_phone
check_phone
phone_validation if phone_changed?
end
def phone_validation
code = Array.new(8){rand(36).to_s(36)}.join
self.phone_verification_code = code
self.save
end
However, this leads to an endless loop. The problem is that the callback is called again after self.save
in the phone_validation method. phone_changed?
apparently still returns true
. How can I change this behaviour?
解决方案
Try this:
User.rb
attr_accessor :phone_checked
after_update :check_phone, :unless => "phone_checked"
check_phone
phone_validation if phone_changed?
end
def phone_validation
code = Array.new(8){rand(36).to_s(36)}.join
self.phone_verification_code = code
self.phone_checked = true # update flag
self.save
end
OR
use with caution: skip callbacks
def phone_validation
code = Array.new(8){rand(36).to_s(36)}.join
self.update_column(:phone_verification_code => code)
end
这篇关于Rails 4:after_update回调导致无限循环的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!
查看全文