Re: creating audit tables - Mailing list pgsql-general

From William Yu
Subject Re: creating audit tables
Date
Msg-id ckqd4h$2hel$1@news.hub.org
Whole thread Raw
In response to Re: creating audit tables  ("Ian Harding" <iharding@tpchd.org>)
List pgsql-general
12/31/9999 would be Y10K problem. :)

Dunno about you but I sorta don't care if somebody has to rewrite my app
  8000 years from now. :)



Ian Harding wrote:

> Oh yes.  I do that a lot for attributes that need a history (last name,
> which changes when you get married, etc)  It is a bit more complicated
> for queries though, since I use null to indicate an unknown end date
> instead of the Y2K problem solution below.
>
> -Ian
>
>
>>>>William Yu <wyu@talisys.com> 10/15/04 12:46 PM >>>
>
> Have you thought about unifying the audit + the current table and add
> from/to datestamps for every record?
>
> Example:
>
> from_dt   to_dt       value
> 9/1/2004  9/30/2004   ABC
> 9/30/2004 10/5/2004   XYZ
> 10/6/2004 12/31/9999  123

pgsql-general by date:

Previous
From: Mike Mascari
Date:
Subject: Avoiding sequential scans with OR join condition
Next
From: Michael Fuhr
Date:
Subject: Re: plpgsql loop not returning value