| From: | Robert Treat <xzilla(at)users(dot)sourceforge(dot)net> |
|---|---|
| To: | Jason Hihn <jhihn(at)paytimepayroll(dot)com> |
| Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Long term read-only records? |
| Date: | 2003-03-27 20:17:35 |
| Message-ID: | 1048796255.13853.1277.camel@camel |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
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 | Jason Hihn | 2003-03-27 20:28:10 | Re: Long term read-only records? |
| Previous Message | Bruno Wolff III | 2003-03-27 20:05:09 | Re: Data conversion in query |