Arturs Zoldners <[EMAIL PROTECTED]> writes:
> I found another bug, which sounds very like the first one:
Hm, looks like no one ever experimented with permissions checking for
subqueries in a rule WHERE clause before. Fixed - thanks for the report!
regards, tom lane
-
Dear Tom,
On Fri, 2004-04-30 at 19:48, Tom Lane wrote:
> Arturs Zoldners <[EMAIL PROTECTED]> writes:
> > -- The following rule prevents user x to update public_data:
> > CREATE RULE log_public AS ON UPDATE TO private_data WHERE (new.a <>
> > old.a) DO INSERT INTO private_log (old_val, new_val) VA
Arturs Zoldners <[EMAIL PROTECTED]> writes:
> -- The following rule prevents user x to update public_data:
> CREATE RULE log_public AS ON UPDATE TO private_data WHERE (new.a <>
> old.a) DO INSERT INTO private_log (old_val, new_val) VALUES (old.a,
> new.a);
This is a known problem. It's fixed for
Hi!
I submited this bug from web interface 27 Apr 2004, but the details were
lost.
The original message was:
>From PostgreSQL 7.4.2 Documentation (34.4. Rules and Privileges):
"...user only needs the required privileges for the tables/views that he
names explicitly in his queries..."
However, i
The following bug has been logged online:
Bug reference: 1142
Logged by: Arturs Zoldners
Email address: [EMAIL PROTECTED]
PostgreSQL version: 7.4
Operating system: Linux (RedHat 9 distrib.)
Description:Problem with update permissions for view
Details:
>From Pos
