Re: security barrier INSERT

From: "Brightwell, Adam" <adam(dot)brightwell(at)crunchydatasolutions(dot)com>
To: Drew Crawford <drew(at)sealedabstract(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: security barrier INSERT
Date: 2014-10-25 02:26:23
Message-ID: CAKRt6CRG6AEHSMn=yBWDAwQiY1ungGsDw6Y58wPRJOAnLwAHmA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Drew,

> IMHO this is nonintuitive, the intuitive behavior of a security_barrier
> view should be to forbid inserting rows that can’t appear in the view.
>

Isn't that what WITH CHECK OPTION is meant to accomplish?

-Adam

--
Adam Brightwell - adam(dot)brightwell(at)crunchydatasolutions(dot)com
Database Engineer - www.crunchydatasolutions.com

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2014-10-25 03:19:04 Re: How ugly would this be? (ALTER DATABASE)
Previous Message Drew Crawford 2014-10-25 02:05:19 security barrier INSERT