Re: Long term read-only records?
От | Dennis Gearon |
---|---|
Тема | Re: Long term read-only records? |
Дата | |
Msg-id | 3E81DEC7.3000306@cvc.net обсуждение исходный текст |
Ответ на | Re: Long term read-only records? (Dennis Gearon <gearond@cvc.net>) |
Ответы |
Re: Long term read-only records?
|
Список | pgsql-general |
OOOPS, record by record, I see. Mabye the flag in combination with a view? Dennis Gearon wrote: > You can also set users to not do things like triggers, views, functions, > etc, and basically leave nothing but SELECT. That won't work? > > 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 >> >> Thank you for your time. >> >> >> ---------------------------(end of broadcast)--------------------------- >> TIP 4: Don't 'kill -9' the postmaster >> > > > ---------------------------(end of broadcast)--------------------------- > TIP 1: subscribe and unsubscribe commands go to majordomo@postgresql.org >
В списке pgsql-general по дате отправления: