From: | Guillaume Lelarge <guillaume(at)lelarge(dot)info> |
---|---|
To: | "bdmytrak(at)eranet(dot)pl" <bdmytrak(at)eranet(dot)pl> |
Cc: | pgadmin-support(at)postgresql(dot)org |
Subject: | Re: column level privilages error |
Date: | 2012-01-30 16:17:20 |
Message-ID: | 1327940240.3223.57.camel@localhost.localdomain |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-support |
On Mon, 2012-01-30 at 13:13 +0100, bdmytrak(at)eranet(dot)pl wrote:
> PostgreSQL provides Error code 01007 (privilege_not_granted) and 01006
> (privilege_not_revoked), is it possible to handle these exceptions?
We never use the error codes. We simply display the error messages from
the server.
And doing an exception for some error codes doesn't seem a good idea.
> I am not sure if codes are used at present (according to
> documentation: "Some are not actually used at present, but are defined
> by the SQL standard." source:
> http://www.postgresql.org/docs/9.1/static/errcodes-appendix.html)
>
>
> Or simply remove this tab (like on table level) if user is not allowed
> to change privilages...
Well, it would be great to be able to use the privileges and make sure
the user cannot do something in the UI that he's not allowed on the
server. When someone will want to do something like this, he'll need to
have a complete patch. Not only the column level privileges. And it
would be a major work AFAICT.
--
Guillaume
http://blog.guillaume.lelarge.info
http://www.dalibo.com
PostgreSQL Sessions #3: http://www.postgresql-sessions.org
From | Date | Subject | |
---|---|---|---|
Next Message | bdmytrak@eranet.pl | 2012-01-30 21:19:28 | Re: column level privilages error |
Previous Message | bdmytrak@eranet.pl | 2012-01-30 12:13:58 | Re: column level privilages error |