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
{{ message }}
This repository has been archived by the owner on Feb 26, 2020. It is now read-only.
It's a nice idea, a gem that allows a simple undelete. However, we should reevaluate which objects we are using it on. Anything that uses acts_as_paranoid should offer an undelete function, otherwise why bother keeping it in the database?
For some objects like votes there is no compelling reason to keep those deleted objects around... IMO they should be deleted immediately. The gem allows us to call irreversible deletes on any object, so we should be using that. See https://github.com/ActsAsParanoid/acts_as_paranoid for how to do this.
For objects we do decide to keep around, it would be a good idea to have a time limit for undeletion, so we don't keep stale objects around forever. Run a cronjob or something like that.
The text was updated successfully, but these errors were encountered:
It's a nice idea, a gem that allows a simple undelete. However, we should reevaluate which objects we are using it on. Anything that uses
acts_as_paranoid
should offer an undelete function, otherwise why bother keeping it in the database?For some objects like votes there is no compelling reason to keep those deleted objects around... IMO they should be deleted immediately. The gem allows us to call irreversible deletes on any object, so we should be using that. See https://github.com/ActsAsParanoid/acts_as_paranoid for how to do this.
For objects we do decide to keep around, it would be a good idea to have a time limit for undeletion, so we don't keep stale objects around forever. Run a cronjob or something like that.
The text was updated successfully, but these errors were encountered: