This removes the assumption from `really_destroy!` that there is
only one column value, the deletion date, that needs to be updated
on a model that is being `really_destroy!`ed. Instead, use the
defined `paranoia_destroy_attributes` as they are used in `destroy`
and other calls.

This prevents an issue where the DBMS will complain when trying to
`really_destroy!` one of these models, given that paranoia is
attempting to insert a DateTime value into a boolean (or otherly-
typed) column.

Fixes #326

This makes paranoia's code itself more explicit.

This should help users be more explicit about what action they want to
perform. My hope is that this will also make it easier to migrate off of
paranoia.

This `defined?(super)` check was introduced for Rails 4.1 support
https://github.com/rubysherpas/paranoia/pull/390#issuecomment-284819747
but we've stopped supporting Rails 4.1 already
https://github.com/rubysherpas/paranoia/pull/393#issuecomment-289227091

Fixes a problem of ambiguous table names when using only_deleted method and joining tables that have a scope on `with_deleted`

Update homepage in gemspec

The homepage is supposed to be where you can find the code. It is displayed on rubygems.org page. Currently it will redirect you back to the same page. Should point at this github repo.

Update README to use proper version for Rails 5

Version 2.2.0

Ignore failures from all jruby's on travis

Add explicit language about dependent: :destroy

Update CHANGELOG.md

update ruby and rails versions

Use ActiveSupport.on_load to correctly re-open ActiveRecord::Base. https://github.com/rubysherpas/paranoia/issues/335

Touch record on paranoia-destroy. Fixes #296

Touch record on destroy by leveraging the paranoia_destroy_attributes.
Applied the same to the restore-method as this eliminates the extra query.

Touch record on destroy by leveraging the paranoia_destroy_attributes.
Applied the same to the restore-method as this eliminates the extra query.

Use ActiveSupport.on_load to correctly re-open ActiveRecord::Base. https://github.com/rubysherpas/paranoia/issues/335

Add a without_deleted scope to manually exclude paranoia-deleted records, which is essentially the paranoia_scope.
Useful when using the option :without_default_scope or the unscoping of a paranoia-model was required.
Aliased it to the paranoia_scope as opposed to the existing with_deleted scope.

Just for consitency. alias_method is easier to reason about than
only_deleted.

In rails 4.x this passed around a set of arel conditions, in rails 5 it
passes around an AR::Relation and uses where().

See rails/rails@5f521cbff3c8a46cfc8e16b234294a20c285d00d

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

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