Skip to content
This repository has been archived by the owner on Feb 26, 2020. It is now read-only.

Reevaluate how we handle our paranoid object deletion #126

Open
krozett opened this issue Jul 28, 2015 · 0 comments
Open

Reevaluate how we handle our paranoid object deletion #126

krozett opened this issue Jul 28, 2015 · 0 comments

Comments

@krozett
Copy link
Collaborator

krozett commented Jul 28, 2015

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.

@jshslsky jshslsky added this to the 1.1.10 milestone Jan 14, 2016
@jshslsky jshslsky modified the milestones: 1.1.10, 1.1.11 Jan 27, 2016
@jshslsky jshslsky modified the milestone: 1.1.11 Apr 4, 2016
# for free to subscribe to this conversation on GitHub. Already have an account? #.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants