Re: Which error constant to use for "permission deny error when updating a table that user is not allowd to "

From: William Leite Araújo <william(dot)bh(at)gmail(dot)com>
To: emilu(at)encs(dot)concordia(dot)ca
Cc: "pgsql general" <pgsql-general(at)postgresql(dot)org>
Subject: Re: Which error constant to use for "permission deny error when updating a table that user is not allowd to "
Date: 2006-04-03 19:44:11
Message-ID: bc63ad820604031244i5b4957bey892fe56888baff8@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Why doesn't test before update?
IF EXISTS( SELECT * FROM information_schema.table_privileges WHERE
grantee = '1' AND table_name = '2' AND privilege_type = 'UPDATE') THEN
...
ELSE
...
END IF;

On 4/3/06, Emi Lu <emilu(at)encs(dot)concordia(dot)ca> wrote:
>
> Hello,
>
> I am trying to catch permission denied exception. For example, user 1 is
> not allowed to update table 2, when user1 updated table 2 there is a
> permission excetpion.
>
> In http://www.postgresql.org/docs/8.1/static/errcodes-appendix.html,
> I tried "modifying_sql_data_not_permitted" , "sql_routine_exception",
> "external_routine_exception" but none of them catch the permission deny
> error.
>
> Could someone tell me which error constant should I use to catch the
> permission denied error please?
>
> Thanks a lot!
> Ying
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 9: In versions below 8.0, the planner will ignore your desire to
> choose an index scan if your joining column's datatypes do not
> match
>

--
William Leite Araújo

In response to

Browse pgsql-general by date

  From Date Subject
Next Message MaRCeLO PeReiRA 2006-04-03 20:35:17 Log Slow Queries
Previous Message Emi Lu 2006-04-03 18:01:33 Which error constant to use for "permission deny error when updating a table that user is not allowd to "