The changes in 40b7af58 were insufficient, this should do the trick.

Remove stranded asterisks.

Change-Id: Ib73e43a5adcb8bd9b5bbf5b7ca60f9865e5415e7

FIX: where("association_id", id) leads to invalid statement in postgres. where should just be given a hash.

Add paranoia_scope as named version of default_scope

This reverts commit 4004bd5e.

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.

raise error for acts_as_paranoid on models without primary keys

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

Fix usage of paranoia_column in related models

refs https://github.com/radar/paranoia/issues/102

Add compatibility info for rails4

hasOne association could not restore

Conflicts:
	test/paranoia_test.rb

Clear association cache

Fix RSpec 3.x deprecations

Reset paranoia_column before updating it. Fixes #153

This appears to be a Rails ~> 4.0.8 bug, which is seemingly fixed in Rails 4.1.

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

really_destroy! and has_one associations