ruby-on-rails – 什么原因导致deprecation警告:ActiveRecord :: Base.raise_in_transactional_callbacks =?

当我运行我的功能规格时,我收到此消息:

DEPRECATION WARNING: ActiveRecord::Base.raise_in_transactional_callbacks= is deprecated,has no effect and will be removed without replacement.

我正在使用Rails 5.0.0.rc1,我不知道是什么是抛出这种弃用警告.

我在我的application.rb文件中有这个.我删除它,弃用警告消失了:

config.active_record.raise_in_transactional_callbacks = true

我想知道这个不推荐警告是什么意思的提示,并且知道什么触发了这种弃用警告.

解决方法

我认为这种行为是在4.1和4.2之间添加的,作为一个不再适用于轨道5的问题的临时解决方案:

http://edgeguides.rubyonrails.org/upgrading_ruby_on_rails.html#error-handling-in-transaction-callbacks

Currently,Active Record suppresses errors raised within
after_rollback or after_commit callbacks and only prints them to the
logs. In the next version,these errors will no longer be suppressed.
Instead,the errors will propagate normally just like in other Active
Record callbacks.

When you define an after_rollback or after_commit callback,you will
receive a deprecation warning about this upcoming change. When you are
ready,you can opt into the new behavior and remove the deprecation
warning by adding following configuration to your
config/application.rb:

config.active_record.raise_in_transactional_callbacks = true

相关文章

validates:conclusion,:presence=>true,:inclusion=>{...
一、redis集群搭建redis3.0以前,提供了Sentinel工具来监控各...
分享一下我老师大神的人工智能教程。零基础!通俗易懂!风趣...
上一篇博文 ruby传参之引用类型 里边定义了一个方法名 mo...
一编程与编程语言 什么是编程语言? 能够被计算机所识别的表...
Ruby类和对象Ruby是一种完美的面向对象编程语言。面向对象编...