| Name | 
 Last commit 
 | 
Last Update | 
|---|---|---|
| lib | ||
| test | ||
| .gitignore | ||
| .travis.yml | ||
| CHANGELOG.md | ||
| CODE_OF_CONDUCT.md | ||
| CONTRIBUTING.md | ||
| Gemfile | ||
| LICENSE | ||
| README.md | ||
| Rakefile | ||
| paranoia.gemspec | 
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
| Name | 
 Last commit 
 | 
Last Update | 
|---|---|---|
| lib | Loading commit data... | |
| test | Loading commit data... | |
| .gitignore | Loading commit data... | |
| .travis.yml | Loading commit data... | |
| CHANGELOG.md | Loading commit data... | |
| CODE_OF_CONDUCT.md | Loading commit data... | |
| CONTRIBUTING.md | Loading commit data... | |
| Gemfile | Loading commit data... | |
| LICENSE | Loading commit data... | |
| README.md | Loading commit data... | |
| Rakefile | Loading commit data... | |
| paranoia.gemspec | Loading commit data... |