Open Stack

Typical cases are user error where someone accidentally deletes an item from a tenant. The image guys have a good structure where images become unavailable and are recoverable for a certain period of time. A regular periodic task cleans up deleted items after a configurable number of seconds to avoid constant database growth.

My preference would be to follow this model universally (an archive table is a nice way to do it without disturbing production).

Tim


> On Tue, Mar 11, 2014, Mike Wilson <geekinutah at gmail.com> wrote:
> > Undeleting things is an important use case in my opinion. We do this
> > in our environment on a regular basis. In that light I'm not sure that
> > it would be appropriate just to log the deletion and git rid of the
> > row. I would like to see it go to an archival table where it is easily restored.
> 
> I'm curious, what are you undeleting and why?
> 
> JE
> 
> 
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev