Functionality and performance questions, and approval recommendation about logidze

[palkan]

Hi @jmkristofzski!

It's difficult to tell from the documentation, does this save the original record, then apply changes every time it is loaded? Or does it save the most recent and contain a log of all past changes?

The first one: the log is stored along with the most recent record's state. So there is no overhead when loading the current version.

In regards to question 1, if the most recent version is saved and all past changes are logged in the log_data column would there be any noticable benefit to saving the log_data in a separate table, then creating a relationship table between log_data and the table you want to track?

You can check the benchmarks here.

We're interested, first of all, in memory usage. Of course, loading the whole history provides an overhead. But this overhead is much less than loading logs from a separate table (as PaperTrail does, for example).

One way to eliminate the overhead completely could be to add log_data to ignored_columns and explicitly select it when necessary.

Is it possible to add an "Approval" feature where someone such as an Admin or Mod must approve changes prior to them being implemented?

The log entry is created in the database, so it would be quite difficult to implement such feature.

[jmkristofzski]

Thank you for the response!

Taking all that into account I think I'll set up the approval process outside of the gem, and once approve make use of the gem to implement the changes.