Sounds like a good idea to me as well. On our two largest projects, we don't
let users permanently delete anything .. ever. We just flag the data that
they 'delete' to not show up any more. Inevitably, someone always deletes
something that they want back. Well, we can certainly get their data back
for them, for a $75 charge for the support call ;) This makes it well worth
the trouble of the little bit of extra coding needed during development.
Besides, hard drive space is cheap.
Todd Ashworth
> > -----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/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
