BETAmodules.com is in beta — open to partnerships & joint ventures.Build with us
modules.com
⌘K

acts_as_archival

v2.1.0RubyGems· Ruby

*Atomic archiving/unarchiving for ActiveRecord-based apps* We had the problem that acts_as_paranoid and similar plugins/gems always work on a record by record basis and made it very difficult to restore records atomically (or archive them, for that matter). Because the archive and unarchive methods are in transactions, and every archival record involved gets the same archive number upon archiving, you can easily restore or remove an entire set of records without having to worry about partial deletion or restoration. Additionally, other plugins generally screw with how destroy/delete work. We don't because we actually want to be able to destroy records.

The verdict
Abandoned. Last published 3 years ago. No recent activity — look for a maintained alternative.
No recent activity — look for a maintained alternative.
Live from the RubyGems registry · derived rules, not AI
How it scores
MaintenanceAbandoned
PopularityNiche
SecurityClean
LicensePermissive
DepsZero deps
Maintenance
Last published 3 years ago.
Popularity
1.1K downloads / week
Security
No known advisories for this version (OSV).
License
MIT
Dependencies
No runtime dependencies
Recent releases
  • 2.1.03 years ago
  • 2.0.04 years ago
  • 1.4.06 years ago
  • 1.3.08 years ago
  • 1.2.09 years ago
  • 1.1.110 years ago
  • 1.1.010 years ago
  • 1.0.010 years ago
acts_as_archival — *Atomic archiving/unarchiving for ActiveRecord-based apps* We had the problem that acts_as_paranoid and similar plugins/gems always work on a record by record basis and made it very difficult to restore records atomically (or archive them, for that matter). Because the archive and unarchive methods are in transactions, and every archival record involved gets the same archive number upon archiving, you can easily restore or remove an entire set of records without having to worry about partial deletion or restoration. Additionally, other plugins generally screw with how destroy/delete work. We don't because we actually want to be able to destroy records. (Ruby / RubyGems) · Modules