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

archival_record

v4.0.1RubyGems· Ruby

*Atomic archiving/unarchiving for ActiveRecord* acts_as_paranoid and similar plugins/gems work on a record-by-record basis and make it difficult to restore records atomically (or archive them, for that matter). Because ArchivalRecord's #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 change how destroy/delete work. ArchivalRecord does not, and thus one can destroy records like normal.

The verdict
Aging — last published over a year ago — check before adopting. Check the repo for activity before adopting.
Check the repo for activity before adopting.
Live from the RubyGems registry · derived rules, not AI
How it scores
MaintenanceAging
PopularityNiche
SecurityClean
LicensePermissive
DepsZero deps
Maintenance
Last published over a year ago — check before adopting.
Popularity
8 downloads / week
Security
No known advisories for this version (OSV).
License
MIT
Dependencies
No runtime dependencies
Recent releases
  • 4.0.1over a year ago
  • 4.0.0over a year ago
  • 3.0.1over a year ago
  • 3.0.0over a year ago
  • 2.0.25 years ago
  • 2.0.15 years ago
  • 2.0.05 years ago
archival_record — *Atomic archiving/unarchiving for ActiveRecord* acts_as_paranoid and similar plugins/gems work on a record-by-record basis and make it difficult to restore records atomically (or archive them, for that matter). Because ArchivalRecord's #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 change how destroy/delete work. ArchivalRecord does not, and thus one can destroy records like normal. (Ruby / RubyGems) · Modules