Content-Type: text/plain;
  charset="iso-8859-1"
From: Josh Berkus <josh@agliodbs.com>
Reply-To: josh@agliodbs.com
Organization: Aglio Database Solutions
To: Luis Sousa <llsousa@ualg.pt>,
	pgsql-sql <pgsql-sql@postgresql.org>
Subject: Re: Permission on insert rules
Date: Mon, 11 Nov 2002 12:12:59 -0800
References: <3DCBF47B.7080809@ualg.pt>
In-Reply-To: <3DCBF47B.7080809@ualg.pt>
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Message-Id: <200211111212.59912.josh@agliodbs.com>


Luis,

> Just a question.
> I'm writing some rules to insert/update some data in my database, and I=
=20
> gave all the privileges on that view to the user, and only select on the=
=20
> tables.
> When that user inserts data using the view, I thought that was user=20
> postgres that will do the rest ! But I got  permission denied on those=20
> tables.
> The idea was to create a layer, with the views, giving to that user=20
> permission on views to insert and update, and not to tables.
> Is this possible ?

I just checked this.  It works fine in 7.2.3.

I think that you are missing a step.  If you want to have an updatable view=
,=20
then you need to define a Rule for updating it, such as:

kitchen=3D# create rule update_password as on update to user_password
kitchen-# do instead update "user" set "password" =3D NEW."password"
kitchen-# where user_id =3D OLD.user_id;

See the online docs, under Server Programming, for how to use the RULES=20
system.

--=20
-Josh Berkus
 Aglio Database Solutions
 San Francisco