You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The cost of this change outweighs the benefits. We'd need to change every database table we have either through multi-stage migration or a downtime. After that, we'd also need to change values inside the JSON blobs in paper_trail history or otherwise we'd need to write history queries like this:
SELECT "log_domains".* FROM "log_domains" WHERE (object->> 'updator_str' = 'somestring' OR object ->> 'updater_str' = 'somestring')
Even when we replace paper_trail with Postgres triggers or any other solution, the history will still be stored as JSON, so the retroactive change would still be necessary.
They might be called
author
andeditor
orcreator
andupdater
instead. There is no such thing as "updator".The text was updated successfully, but these errors were encountered: