Can we therefore make that no removal of deleted column is permitted if there is no implementation of shadow tables ?
Tim From: Joe Gordon [mailto:[email protected]] Sent: 11 March 2014 20:57 To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [all][db][performance] Proposal: Get rid of soft deletion (step by step) On Tue, Mar 11, 2014 at 12:43 PM, Tim Bell <[email protected]<mailto:[email protected]>> wrote: 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). That was the goal of the shadow table, if it doesn't support that now then its a bug. Tim > On Tue, Mar 11, 2014, Mike Wilson > <[email protected]<mailto:[email protected]>> 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 > [email protected]<mailto:[email protected]> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev _______________________________________________ OpenStack-dev mailing list [email protected]<mailto:[email protected]> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
_______________________________________________ OpenStack-dev mailing list [email protected] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
