From: | Dan Lyke <danlyke(at)flutterby(dot)com> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: DELETE and efficiency |
Date: | 2001-03-08 20:38:44 |
Message-ID: | 15015.60884.719975.768541@wynand.flutterby.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Michelle Murrain writes:
> Is that so? If so, that means there might be a way to do an
> undelete? What is it?
As I understand it there's no way to do an undelete because of the way
that transactions get handled, but it does suggest that there are
places where a "deleted char(1)" (or however you want to implement it)
field can be quite handy, especially given the ridiculously cheap
price of disk space (modulo backup...) nowadays.
In applications, confirmation is a cop-out for those too lazy to
implement undo (okay, that's overstating the case a bit), but
structuring your data to acknowledge this at the beginning can be a
worthwhile exercise.
Dan
From | Date | Subject | |
---|---|---|---|
Next Message | Gilles DAROLD | 2001-03-08 20:54:19 | Shell env and PL/SQL |
Previous Message | Tom Lane | 2001-03-08 20:30:55 | Re: inheritance and primary/foreign keys |