This will allow to detect counter cached columns changes in callbacks like `after_destroy` or `after_commit on: :destroy`.
My goal is Rails 4.2 support and it works well with Rails 4.2. I’m leaving this bug not fixed for Rails 4.1 for the time being.
This is a workaround actually. Since `ActiveRecord::CounterCache.each_counter_cached_associations` is private. We shouldn’t use it. Proposals for the proper fix are welcome. The reason the previous version stopped working is `affected_rows` returns `0` at [active_record/counter_cache.rb#L142](https://github.com/rails/rails/blo b/ef99d4cd3ecc58a8c1484740b2fb5447dbda23ab/activerecord/lib/active_recor d/counter_cache.rb#L142). If you follow the method call you’ll find that it’s called at [active_record/persistence.rb#L486](https://github.com/rails/rails/blob/ ef99d4cd3ecc58a8c1484740b2fb5447dbda23ab/activerecord/lib/active_record/ persistence.rb#L486). Probably we’d better override the return value in `ActiveRecord::Relation.delete_all` at [active_record/relation.rb#L481](https://github.com/rails/rails/blob/ef9 9d4cd3ecc58a8c1484740b2fb5447dbda23ab/activerecord/lib/active_record/rel ation.rb#L481).
…che column update
http://edgeguides.rubyonrails.org/4_2_release_notes.html#active-record-d eprecations > Deprecated passing Active Record objects to .find or .exists?. Call id on the objects first. Commits in Rails: rails/rails@d92ae6c 0bd270 rails/rails@d35f003 9596f7 rails/rails@c0609dd 356b35
I think this advice is misleading for most datasets and most RDBMS this is not necessary, and as per #206 doesn't even work. I have moved it to the wiki https://github.com/radar/paranoia/wiki/Custom-sentinel-values
This is a test for a case when a model has a has_one association with an after_validation callback, and we have failed validation. Paranoia will attempt to touch the deleted_at column on the child record that has been built but not saved. Fixes #180