It is unnecessary to test the AR internals here. Testing the
where_values_hash should be sufficient.

We are switching to support of ruby 2.0 and greater. We will only
support jruby OVER 9000 for feature parity.

alias defines these on ActiveRecord::Base itself, which is not what was
intended. This behaviour previous differed between MRI and jruby.

Added without_default_scope option

Fix typo in readme

Update location of acts_as_paranoid repository

Fix grammar and typos in README

Adds changes in 2.1.5 and adds placeholders for missing release notes.

Fix really_destroy! for ruby 2.3

For some reason in ruby 2.3 this definition was interpreted as private.
There was no reason to be defining it where it was, so I've moved it
into the paranoia module.

Use TravisCI's container infrastructure

This makes the startup time for tests much faster.

This also fixes an issue where bundle install would fail because the
version on travis's legacy infrastructure is too old.

See: https://github.com/bundler/bundler/issues/3558

We're still looking for people to help, but a maintainer now exists

Touching record when restored.

Using guard clauses.

Simplify description in README

I had a hard time comprehending the old wording. I think this is easier to read.

Simplify test setup

* Rely on bundler/setup to setup the load paths

Fixed issue #258: uniqueness validator now works with custom active c…

Introduce #paranoia_destroy_attributes and #paranoia_restore_attributes extension points

Use update_columns rather than touch to update the record, for
generality

Unlike touch, update_columns does not create a transaction for
itself, so we need to add the record to the transaction, if present.
If there is not a current_transaction, the add is a no-op.

This all means that delete will not invoke a transaction or run the
after_commit callbacks unless called from within one, which is
consistent with the Rails docs and the behavior of
ActiveRecord::Base#delete.