Thanks for all of the replies to my "Undo Delete" post. Here's a summary
(some items contradict others). Of course, further comments are welcome.
* Do a "soft" rather than a "hard" delete. That is, flag the data as
unavailable but leave it in the database.
* Timestamp the soft deletion.
* Charge lots of money to restore it. (I like this one.)
* Change a soft delete to a hard delete after some time has passed.
* Migrate the soft deletes off to another table.
* Use a view to hide the soft deletes.
* Use a "status" flag to allow for states other than valid/invalid.
* Display an "Undo" button for immediate restoration. None of that "Are
you SURE you want to delete this record?")
-David
> -----Original Message-----
> From: David Shadovitz [mailto:[EMAIL PROTECTED]]
> Sent: Saturday, December 16, 2000 6:52 PM
> To: CF-Talk
> Subject: OT: Undo Delete
>
> I'm thinking of changing my typical "Delete" button so that
> it doesn't actually delete a record, but rather flags it as a
> record to be ignored. I'd also record the date/time that it
> was flagged. That way I can offer the user the opportunity
> to Undo the Delete. I'll probably schedule a job to delete
> all records which have been flagged for more than 1 day.
>
> Hey, I've been influenced by Jef Raskin's "The Humane
> Interface" and Alan Cooper's "The Inmates are Running
> the Asylum."
>
> Any thoughts?
>
> Here's another use for flagging records: Our db tables
> which contain scientific data contain an "approved" field,
> whose default value is "false". After data is inserted into
> the database, an analyst checks it out, and then we toggle
> the flag to "true". Of course, our non-admin canned queries
> all include "WHERE approved = true".
>
> -David
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
Archives: http://www.mail-archive.com/cf-talk@houseoffusion.com/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
