Question 1

How to set up DestroyedAt in a Rails app?

Accepted Answer

First, add the gem to your Gemfile and run bundle install. Then, include the DestroyedAt module in your ActiveRecord models and create a migration to add a destroyed_at datetime column to the corresponding tables, as per the README.

Question 2

DestroyedAt vs acts_as_paranoid: which is better for Rails?

Accepted Answer

DestroyedAt is simpler and more modern, focusing on timestamp-based soft deletes with restoration and callbacks. acts_as_paranoid is older and may have different behavior; choose based on your Rails version and need for minimal dependencies or specific features.

Question 3

Does DestroyedAt work with Rails 7?

Accepted Answer

Yes, DestroyedAt is compatible with recent Rails versions, but always check the gem's GitHub page or documentation for specific compatibility notes, as it's actively maintained by DockYard.

Question 4

How to handle unique emails with DestroyedAt?

Accepted Answer

You need to modify your uniqueness validators manually, such as validates :email, uniqueness: { conditions: -> { where(destroyed_at: nil) } }, because the gem doesn't automatically adjust Rails' default scoping for validators.

Question 5

Can I restore multiple records at once with DestroyedAt?

Accepted Answer

The gem provides instance-level restore methods; for batch restoration, you can iterate over destroyed records using the .destroyed scope and call restore on each, but there's no built-in bulk restore feature.

Question 6

What are the performance impacts of using DestroyedAt?

Accepted Answer

Without proper indexing on the destroyed_at column, queries may slow down due to table scans. The README recommends adding indexes, especially for large datasets, to maintain performance.

Destroyed At

What is Destroyed At?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions