[wp-hackers] Data recovery (post_status?)
davebytes at comcast.net
Sat Feb 11 22:07:46 GMT 2006
Agreed. And, with the move to make more things varchar for extensibility,
here's a vote to move post_status away from being an enum.
post_status=='trash' would probably do fine for this. or ".trash" (would be
nice to have a convention for hiding certain status 'classes' from the
normal view queries without explicitly listing the states to exclude...).
Thoughts? (esp Ryan? given the recent status=='future' changes...)
While we're at it, how about making the comment_approved a varchar too... ;)
----- Original Message -----
From: "Kimmo Suominen" <kimmo+key+wordpress.c4f53f at suominen.com>
To: <wp-hackers at lists.automattic.com>
Sent: Saturday, February 11, 2006 4:44 PM
Subject: Re: [wp-hackers] Data recovery
| On Sat, Feb 11, 2006 at 09:37:26PM +0000, David House wrote:
| > On 11/02/06, Podz <podz at tamba2.org.uk> wrote:
| > > Users are used to a recycle bin, and gearing WP toward multiple users
| > > would seem a decent option to be able to recover anything deleted
| > > a timescale set by the blog owner.
| > > As usual I haven't the slightest clue how to do it, but I would
| > > such a feature would be well received.
| > Another use for an integrated cron. Once a week/month, we could just
| > garbage-collect on a wp-trash table.
| Rather than copy data around in the database, using flag fields would
| be more efficient. Also makes it possible to recover to the same ID,
| since the data never leaves the table until garbage collect time.
More information about the wp-hackers