Don't delete your records, move them to a different table.
acts_as_paranoid, but doesn't mess with your SQL queries.
gem install acts_as_archive
Add to models
acts_as_archive to your models:
class Article < ActiveRecord::Base acts_as_archive end
Next time you run
rake db:migrate, your archive tables will be created automatically.
delete_all like you normally would.
Records move into the archive table instead of being destroyed.
Automatically archive relationships
acts_as_archive model's relationship has the
:dependent option and also uses
acts_as_archive, that relationship will archive automatically.
To use this feature, you must declare your relationships before the
acts_as_archive call within your model!
What if my schema changes?
New migrations are automatically applied to the archive table.
No action is necessary on your part.
Query the archive
::Archive to your ActiveRecord class:
Delete records without archiving
Use any of the destroy methods, but add a bang (!):
Article::Archive.first.destroy! Article.delete_all!([ "id in (?)", [ 1, 2, 3 ] ])
Restore from the archive
Use any of the destroy/delete methods on the archived record to move it back to its original table:
Article::Archive.first.destroy Article::Archive.delete_all([ "id in (?)", [ 1, 2, 3 ] ])
You will find an extra
deleted_at datetime column on the archive table.
You may manually add a
restored_at datetime column to the origin table if you wish to store restoration time as well.
Migrate from acts_as_paranoid
Add this line to a migration, or run it via
This copies all records with non-null
deleted_at values to the archive.
There is a wiki entry that describes the development setup in-depth.