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.brightw...@crunchydatasolutions.com
Database E
Hi guys, I’m seeing some non-intuitive behavior with the new updateable
security barrier views in 9.4. Below is the behavior of 9.4b3:
> =# create table widget ( id integer);
> CREATE TABLE
> =# create view widget_sb WITH (security_barrier=true) AS SELECT * from widget
> where id = 22;
> CREATE
