Tom Lane wrote:
> >>>> Is there any chance to restrict the direct updates of any user to the
> >>>> "stock" table?
> >>>> So that the information in the "stock" table should be updated ONLY by
> >>>> those triggers?
> > But wouldn't be nice if PostgreSQL could offer a more elegant solution?
> Can't you do it with the normal GRANT/REVOKE access-control mechanism?
No. It didn't worked, that was my first idea!
> I'm pretty sure that for rules (views), the access rights for queries
> issued within the rule are checked based on the owner of the rule, not
> the user who invoked the rule. Triggers ought to work the same way,
> though I haven't tried it. So you could make the trigger function and
> the protected table owned by the same user, and then not grant write
> permission on that table to anyone else.
It seems it didn't work!
In response to
pgsql-interfaces by date
|Next:||From: Mario Medina Nussbaum||Date: 2000-02-17 21:54:52|
|Subject: ODBC and PHP (on Linux)|
|Previous:||From: Guido Goldstein||Date: 2000-02-17 17:31:55|
|Subject: Re: [INTERFACES] link problems when inheriting from libpq++|