From 25a96234220a0b0ba37934e62102ebc0be270431 Mon Sep 17 00:00:00 2001 From: Rystraum Gamonez Date: Tue, 14 Jan 2014 01:29:26 +0800 Subject: Updated Changelog to reflect removal of :dependent => :restrict Based on https://github.com/rails/rails/issues/2502, the option has been removed. --- guides/source/upgrading_ruby_on_rails.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/guides/source/upgrading_ruby_on_rails.md b/guides/source/upgrading_ruby_on_rails.md index bca1d36ab7..72a4bb4c2d 100644 --- a/guides/source/upgrading_ruby_on_rails.md +++ b/guides/source/upgrading_ruby_on_rails.md @@ -614,6 +614,10 @@ config.active_record.mass_assignment_sanitizer = :strict Rails 3.2 deprecates `vendor/plugins` and Rails 4.0 will remove them completely. While it's not strictly necessary as part of a Rails 3.2 upgrade, you can start replacing any plugins by extracting them to gems and adding them to your Gemfile. If you choose not to make them gems, you can move them into, say, `lib/my_plugin/*` and add an appropriate initializer in `config/initializers/my_plugin.rb`. +### Active Record + +Option `:dependent => :restrict` has been removed from `belongs_to`. If you want to prevent deleting the object if there are any associated objects, you can set `:dependent => :destroy` and return `false` after checking for existence of association from any of the associated object's destroy callbacks. + Upgrading from Rails 3.0 to Rails 3.1 ------------------------------------- -- cgit v1.2.3