Question 1

How does Logidze compare to PaperTrail for Rails?

Accepted Answer

Logidze uses PostgreSQL triggers for faster, database-level logging with in-column storage, avoiding extra tables. However, it lacks PaperTrail's built-in deletion tracking and is PostgreSQL-only, while PaperTrail supports multiple databases but can be slower.

Question 2

How to attach a user ID to changes in Logidze?

Accepted Answer

Wrap save operations in Logidze.with_responsible(user.id), which stores the ID in the log metadata. You can then access it via log_data.responsible_id and build custom methods to fetch the user object.

Question 3

Does Logidze work with soft delete gems like Discard?

Accepted Answer

Yes, but Logidze itself doesn't handle deletions; you need to use soft-delete tools to keep records in the database. This way, changes are preserved, but Logidze won't log the deletion event itself.

Question 4

Can Logidze track only specific columns to reduce log size?

Accepted Answer

Yes, use the --only or --except options during model generation to limit logged columns. For example, rails generate logidze:model Post --only=title,body tracks only those columns.

Question 5

What happens if I delete a record with Logidze enabled?

Accepted Answer

The entire change history is lost, as Logidze only stores logs in the record's JSONB column. The README recommends using soft-delete gems if you need to retain audits after deletion.

Question 6

How to upgrade Logidze without breaking existing logs?

Accepted Answer

Run rails generate logidze:install --update to update core functions, and regenerate model triggers with --update flag. Always back up data first, as some versions may have breaking changes noted in the upgrading guide.

Logidze

What is Logidze?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions