I do not think this is entirely uncommon. I have come across situations
like this before. I say go for it.
On the current project I'm working on (an e-commerce site) the
product list is completely replaced every few months. Yet, we want
to keep a list of all the old products, for order histories and such.
However, we do not want to show any old products to the user shopping
on the site.
David Shadovitz wrote:
>
> 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
