Re: Long term read-only records?
От | Jason Hihn |
---|---|
Тема | Re: Long term read-only records? |
Дата | |
Msg-id | NGBBLHANMLKMHPDGJGAPCELECFAA.jhihn@paytimepayroll.com обсуждение исходный текст |
Ответ на | Re: Long term read-only records? (Robert Treat <xzilla@users.sourceforge.net>) |
Список | pgsql-general |
Thank you all for your help. I've been working with MySQL too long. ;-) > -----Original Message----- > From: Robert Treat [mailto:xzilla@users.sourceforge.net] > Sent: Thursday, March 27, 2003 3:18 PM > To: Jason Hihn > Cc: pgsql-general@postgresql.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 > >
В списке pgsql-general по дате отправления: