"Delete" considered harmful, change to "Lock" or remove entirely?

[myself248]

i3Detroit's instance has just suffered another data problem apparently caused by inappropriate use of the Delete button. (Member record deleted instead of setting a plan end date.) I'm starting to think there are no appropriate uses, and the function should be removed. I think #344 is about fixing the delete function, but instead of giving it additional functionality (which is closely tied to business logic about how to handle payments, etc), I'm opening this issue as an alternate solution -- it would be easier and better to simply remove the delete function.

[elplatt]

A good solution might be to add a "deleted" datetime to each table and add
a "is null" check to all of the select queries. Then to delete we'd just
set the delete datetime. If we needed to go back and review or undelete it
would be easy to do that through sql.

On Wed, Jan 14, 2015 at 11:11 AM, myself248 notifications@github.com
wrote:

i3Detroit's instance has just suffered another data problem apparently
caused by inappropriate use of the Delete button. (Member record deleted
instead of setting a plan end date.) I'm starting to think there are no
appropriate uses, and the function should be removed. I think #344
#344 is about fixing the
delete function, but instead of giving it additional functionality (which
is closely tied to business logic about how to handle payments, etc), I'm
opening this issue as an alternate solution -- it would be easier and
better to simply remove the delete function.

—
Reply to this email directly or view it on GitHub
#345.

Edward L. Platt
http://elplatt.com
http://civic.mit.edu/users/elplatt
http://i3detroit.com
@elplatt http://twitter.com/elplatt

This electronic mail message was sent from my desktop personal computer.
Please forgive any long-winded, overly-prosaic ramblings.

[mjgardes]

I like it. It would be nice to have a reason for deletion text column too.