Chris Hoover wrote:
> Just curious, what sort of field do they use to mark the rows? I'm
> assuming a timestamp since it would half to be part of the primary key,
> or am I way off? This has really gotten me thinking about how I might
> implement this in my database.
I do this on a number of tables in my database, I use a byte to store a
status, with each 'bit' meaning something, usually the 128 bit indicates
deleted, so any value over 128 means the record is not current and that
is tested for in any standard queries.
This doesn't get around allowing multiple rows with the same data, with
one being current and the rest deleted - but that's not an issue in my
system. If it's deleted it's deleted, it doesn't get recreated, but can
be restored, thus not using an actual delete fits my scenario quite well.
In response to
pgsql-admin by date
|Next:||From: Robert Treat||Date: 2007-06-01 02:30:50|
|Subject: Re: PostgreSQL Training?|
|Previous:||From: Chris Hoover||Date: 2007-05-31 19:10:13|
|Subject: Re: Deletes hurt|