From: | Jason Hihn <jhihn(at)paytimepayroll(dot)com> |
---|---|
To: | Robert Treat <xzilla(at)users(dot)sourceforge(dot)net> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Long term read-only records? |
Date: | 2003-03-27 20:28:10 |
Message-ID: | NGBBLHANMLKMHPDGJGAPCELECFAA.jhihn@paytimepayroll.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Thank you all for your help. I've been working with MySQL too long. ;-)
> -----Original Message-----
> From: Robert Treat [mailto:xzilla(at)users(dot)sourceforge(dot)net]
> Sent: Thursday, March 27, 2003 3:18 PM
> To: Jason Hihn
> Cc: pgsql-general(at)postgresql(dot)org
> Subject: Re: [GENERAL] Long term read-only records?
>
>
> On Wed, 2003-03-26 at 11:34, Jason Hihn wrote:
> > Is there a way to make a record read-only for months or years?
> My intent is
> > that after a cutoff (a program can run making rows r/o)
> existing records can
> > no longer be modified without unlocking first. User security is
> > insufficient, since that only applies to tables. I'd rather not have to
> > maintain a R/O flag (or date) in code, because it relies on correct,
> > voluntary implementation every time. I'd like something more enforceable
> > then that, and that has me looking to the DBMS
>
> Create a rule or trigger on the table to check the age of a date column
> and then either disregard or allow updates.
>
> Robert Treat
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Daniel R. Anderson | 2003-03-27 20:32:00 | Error Message while Trying To Run A Compiled libpq.h file. |
Previous Message | Robert Treat | 2003-03-27 20:17:35 | Re: Long term read-only records? |