百科.dev
全部条目在线工具AI 编程趋势榜开源项目技术资讯提交条目
登录
< 返回工具列表
P

permanent_records

> 编程语言
开源

Rails 插件 - 软删除您的 ActiveRecord 记录。它类似于 ActsAsParanoid 的明确版本。

273 stars0 点赞2 次浏览
访问官网GitHub

工具介绍

Rails 插件 - 软删除您的 ActiveRecord 记录。它类似于 ActsAsParanoid 的明确版本。

PermanentRecords

http://github.com/JackDanger/permanent_records/

This gem prevents any of your ActiveRecord data from being destroyed. Any model that you've given a "deleted_at" datetime column will have that column set rather than let the record be deleted.

Requirements

We currently support Ruby >= 3.2 and Rails >= 7.1. See .github/workflows/test_and_lint.yml for the exact Ruby/Rails combinations tested in CI.

If you need older Ruby / Rails versions, pin to permanent_records ~> 6.0 (Ruby 2.7-3.2 / Rails 5.2-7.1).

What methods does it give me?

ruby
User.find(3).destroy          # Sets the 'deleted_at' attribute to Time.now
                              # and returns a frozen record. If halted by a
                              # before_destroy callback it returns false instead

User.find(3).destroy(:force)  # Executes the real destroy method, the record
                              # will be removed from the database.

User.destroy_all              # Soft-deletes all User records.

User.delete_all               # bye bye everything (no soft-deleting here)

There are also two scopes provided for easily searching deleted and not deleted records:

ruby
User.deleted.find(...)        # Only returns deleted records.

User.not_deleted.find(...)    # Only returns non-deleted records.

Note: Your normal finds will, by default, include deleted records. You'll have to manually use the not_deleted scope to avoid this:

ruby
User.find(1)                  # Will find record number 1, even if it's deleted.

User.not_deleted.find(1)      # This is probably what you want, it doesn't find deleted records.

Can I easily undelete records?

Yes. All you need to do is call the 'revive' method.

ruby
User.find(3).destroy         # The user is now deleted.

User.find(3).revive          # The user is back to it's original state.

And if you had dependent records that were set to be destroyed along with the parent record:

ruby
class User < ActiveRecord::Base
  has_many :comments, dependent: :destroy
end

User.find(3).destroy         # All the comments are destroyed as well.

User.find(3).revive          # All the comments that were just destroyed
                             # are now back in pristine condition.

Forcing deletion works the same way: if you hard delete a record, its dependent records will also be hard deleted.

Can I use default scopes?

ruby
default_scope { where(deleted_at: nil) }

If you use such a default scope, you will need to simulate the deleted scope with a method

ruby
def self.deleted
  self.unscoped.where('deleted_at IS NOT NULL')
end

Is Everything Automated?

Yes. You don't have to change ANY of your code to get permanent archiving of all your data with this gem. When you call destroy on any record (or destroy_all on a class or association) your records will all have a deleted_at timestamp set on them.

Upgrading from 3.x

The behaviour of the destroy method has been updated so that it now returns false when halted by a before_destroy callback. This is in line with behaviour of ActiveRecord. For more information see #47.

Productionizing

If you operate a system where destroying or reviving a record takes more than about 3 seconds then you'll want to customize PermanentRecords.dependent_record_window = 10.seconds or some other value that works for you.

Patches welcome, forks celebrated.

Copyright 2015 Jack Danger Canty @ https://jdanger.com released under the MIT license

Issues· 16 开放

查看全部 Issues在 GitHub 打开

暂无开放 Issues,或尚未同步最近议题。

> 标签

Ruby

暂无评论,来聊聊你的看法吧

> 工具信息

发布日期2026年8月1日
最后更新2026年9月18日
分类编程语言
定价开源

> 相关工具

T
TypeScript
JavaScript 的超集,为前端与全栈提供静态类型
P
Python
通用编程语言,广泛用于 Web、数据与 AI
G
Go
Google 推出的简洁高效系统语言