> Just as an aside, when I use this approach I find it handy to use a
> date field, 'deletedate' rather than a flag. This provides the extra
> bit about when an item was deleted, which can sometimes be useful
> later information on.
And since you brought it up . . . a deleted_by field. Because this
situation never seems to stop happening:
"Why is it deleted!?! It's not supposed to be deleted, and the client
is very upset! Very upset!"
"Um . . . because somebody deleted it. Don't you know? Don't you manage that?"
"Well . . . yes, it is my job. But I didn't delete it. It's not
supposed to be deleted. There must be something wrong with the
application!"
"Yeah, well, the log says you deleted it, and the flag says you
deleted it. So unless somebody else was logged in as you . . . "
"Oh, wait. When was it deleted?"
"2 weeks ago."
"Nevermind. Umm . . . If you could just reactivate that for me."
Of course, this will almost certainly be followed up with an email
where the topic is a very vague notion of "lessons learned", "being
more careful", and "accountability".
--
-Ben
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---
