I asked about `restore` in the
[Notes](https://github.com/radar/paranoia/pull/192#issue-51914917) of
the PR's description. Personally I don't need such a behaviour. So
removing.

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 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

This allows testing rails 4.0 on ruby 2.2

We no longer have different behaviour between AR versions.

Thanks @kidlab

There was a change in ActiveRecord#update_columns on latest rails
so now it checks for `destroyed?` instead of `persisted?`. Paranoia
can't override `destoyed?` like this anymore otherwise
`update_columns` will always raise:

        ActiveRecord::ActiveRecordError: cannot update a destroyed record

see https://github.com/rails/rails/commit/0f99aa615e11c50cc64b567f54cf64f59108c5e5

To ensure that we are using the association _type in our scope.

Restoring polymorphic has_one relationships errored because paranoia was
not correctly looking up the foreign_key.

Output from failing test -

ActiveRecord::StatementInvalid: SQLite3::SQLException: no such column: parent_model_id: SELECT  "polymorphic_models".* FROM "polymorphic_models" WHERE ("polymorphic_models"."deleted_at" IS NOT NULL) AND (parent_model_id)  ORDER BY "polymorphic_models"."id" ASC LIMIT 1

The test sets up a PolymorphicModel, which has_many parents. The
ParentModel then has a has_one relationship with PolymorphicModel. When
restoring, the foreign key is set as - `self.class.name.to_s.underscore_id`
which will be parent_model_id, instead of the :as option.

DEPRECATION WARNING: Currently, Active Record suppresses errors raised within `after_rollback`/`after_commit` callbacks and only print 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.

apply the deprecation fix for ActiveRecord >= 4.2 only

DEPRECATION WARNING: You are passing an instance of ActiveRecord::Base to `find`. Please pass the id of the object by calling `.id`. (called from block in restore at /Users/sergey/ruby_projects/paranoia/lib/paranoia.rb:38)

Change-Id: Ib73e43a5adcb8bd9b5bbf5b7ca60f9865e5415e7

Regression from 6881e750

We need to be able to load our class definitions without having an
available database connection.

Change connect! to setup!, so that we can use connect! to give us an
empty DB with no tables.

Use ensure where appropriate to ensure that tests after that one can run
even if it fails.

This reverts commit 6881e750.

see https://github.com/radar/paranoia/issues/169

Use fetch for sentinel_value

Use DateTime for sentinel_value example

Use an epoch. rails convers '0' or 0 to nil for datetime fields

Add test for restore

Update readme

Move MYSQL note to bottom of readme

update destroyed? for sentinel value

This reverts commit 566b1cbd.

Conflicts:
	README.md
	test/paranoia_test.rb

Fixes #149

Fixes #148

Fixes #143

Fixes #138

Removed deprecated assert_nothing_raised from test.

when the model has_one use class_name or foreign_key, restore use
class_name or setting the foreign_key.