mongoid-history VS PaperTrail

mongoid-history

We haven't tracked posts mentioning mongoid-history yet.
Tracking mentions began in Dec 2020.

PaperTrail

• RDS Database Migration Series - Facing The Giant: How we migrated 11 TB database
  2 projects | dev.to | 13 May 2024

  The primary culprits were two tables (and their huge indexes) that contributed approximately 90% to the total size of the database. One of them was an audit trail (paper trail versions, to be exact), and the second one was more domain-specific for short-term rentals. It's a pre-computed cache of prices for properties depending on various conditions so that they don't need to be computed each time on the fly and can be easily distributed to other services.

• historical data and "point in time" data modeling techniques, advice.
  1 project | /r/dataengineering | 28 Jun 2023

  if the source (web) application makes their own audit tables. ex: our ruby on rails application uses the paper-trail gem

• Best rails tools to automatically handle logging of things like all a user's actions, or changes to a record in a module - primarily for audit purposes.
  3 projects | /r/ruby | 9 Mar 2023

  Start with https://github.com/paper-trail-gem/paper_trail

  4 projects | /r/rails | 9 Mar 2023
• Inventory/Sales Management module built on a Rails app - what would be the best way to "version" updates made against an SKU.
  1 project | /r/rails | 27 Dec 2022

  We use paper_trail for this

• is there a gem for tracking adhoc rails console changes
  2 projects | /r/rails | 15 Dec 2022

  I think you could use that in conjunction with the paper_trail gem, as /u/GreenCalligrapher571 mentioned, which is also a good suggestion. As an additional note, when changing records in production while using the paper_trail gem, I suggest wrapping your database-mutating statements executed in the rails console within a whodunnit block, so PaperTrail.request(whodunnit: 'Dorian Marié') { widget.update name: 'Wibble' } or something rather than just widget.update name: 'Wibble'. Or, if you have some sort of issue-tracking / ticketing system, you could set the whodunnit value to the ticket number or whatever, and then anyone who wants to know why the records are in the state they're in can consult that ticket, which hopefully has additional relevant context.

• History Tracking With Postgres
  1 project | dev.to | 25 Oct 2022

  For a while we did this using the paper-trail gem. This was a very simple way to add a few lines of code to keep track of all of the changes made to an ActiveRecord model. But it came with one drawback. Every change to the data had to be done through ActiveRecord. There are often times when this makes an app vulnerable to a race condition. I’ll use a contrived example so as not to share any real code from our client’s app.

• Adding soft delete to a Phoenix Commanded (CQRS) API
  3 projects | dev.to | 1 Jun 2022

  In most designs, this would probably not be possible unless a table tracking extension is being used in an ORM. Even with change tracking enabled through extensions like paper trail or Django simple history, it can be tricky to restore deleted entities. Object tracking would need to have been enabled before it is needed to ensure the data is still around to be restored.

• Looking for a Rails Gem that Audits Manual Database Changes
  2 projects | /r/rails | 23 May 2022
• Temporality/time-travelling in DB with ActiveRecord?
  3 projects | /r/rubyonrails | 16 May 2022

  Maybe you are looking for the papertrail gem? https://github.com/paper-trail-gem/paper_trail