Re: [HACKERS] SE-PostgreSQL and row level security

2009-02-18 Thread BogDan Vatra
Pavel Stehule wrote: 2009/2/17 Josh Berkus j...@agliodbs.com: All, I thought we'd agreed to compromise on having SE without row-level in 8.4, and working on SE with row-level in 8.5. Why are we revisiting this argument? 8.4 is *already* late; arguing further about the terms of SE simply

Re: [HACKERS] SE-PostgreSQL and row level security

2009-02-15 Thread BogDan Vatra
On Fri, Feb 13, 2009 at 02:29:39PM +0200, BogDan Vatra wrote: [..] A message for postgresql decision board: Dear postgresql hackers, if I can do something to push row level acl for 8.4 please tell me, I do anything to have this feature, it will help me, and I hope many others

Re: [HACKERS] SE-PostgreSQL and row level security

2009-02-13 Thread BogDan Vatra
[..] A message for postgresql decision board: Dear postgresql hackers, if I can do something to push row level acl for 8.4 please tell me, I do anything to have this feature, it will help me, and I hope many others, this feature will help to develop client to postgres applications without

Re: [HACKERS] SE-PostgreSQL and row level security

2009-02-11 Thread BogDan Vatra
Hi, [...] In my understanding, the row-level ACLs feature (plus a bit enhancement) can help your requirements. I developed it with SE-PostgreSQL in parallel, but also postponed to v8.5 series. It enables to assign database ACLs on individual tuples, and filter out violated tupled from the

[HACKERS] SE-PostgreSQL and row level security

2009-02-10 Thread BogDan Vatra
or the possibility to CHECK a cell of a row with a subquery in our example something like this:CHECK (id_customer IN (select id from view_customers)). If I'll have this feature I don't have to create that triggers anymore. I hope this is more simple for you to create. Yours, BogDan Vatra, -- Sent via pgsql