really_destroy! and has_one associations
Merge pull request #151 from astronz/really-destroy-has-one

really_destroy! and has_one associations
Revert "option column for flagging deletes allowing unique keys to work properly"

This reverts commit 566b1cbd479b061ef41d79b8e345da7351d1d933.

Conflicts:
	README.md
	test/paranoia_test.rb
Add optional sentinel_value

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
Do not restore if attributes are frozen

This appears to be a Rails ~> 4.0.8 bug, which is seemingly fixed in Rails 4.1.
Reset paranoia_column before updating it. Fixes #153
Merge pull request #154 from wioux/rails4

Reset paranoia_column before updating it. Fixes #153
Replace deprecated RSpec failure_message_for_should syntax
Rephrase matcher failure messages according to RSpec 3 style
Retain compatibility with RSpec 2 matchers
Merge pull request #156 from lime/rspec-deprecations

Fix RSpec 3.x deprecations
Do not throw an exception when we are trying to destroy a nonpersisted soft-delete model.
IDE whitespace fail.
Just a test to ensure that ActiveRecord does not throw an exception when destroying new records.
IDE Whitespace fail again.