微信公众号搜"智元新知"关注
微信扫一扫可直接关注哦!

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

原文地址:https://www.jb51.cc/ruby/271747.html

版权声明:本文内容由互联网用户自发贡献,该文观点与技术仅代表作者本人。本站仅提供信息存储空间服务,不拥有所有权,不承担相关法律责任。如发现本站有涉嫌侵权/违法违规的内容, 请发送邮件至 dio@foxmail.com 举报,一经查实,本站将立刻删除。

相关推荐