On Mon, 2012-01-30 at 22:19 +0100, bdmyt...@eranet.pl wrote:
> You handle it somehow for tables (there is no privilage tab in table
> properies when You cannot change privilages). I suppose it is done
> based on ACL for table.
No. On PostgreSQL, it depends if you are superuser or an owner. There
a
ARNING, so maybe it is good idea to treat WARNINGS in the same way
as ERRORS?
Hope You will find elegant solution.
Regards,
Bartek
--- Oryginalna wiadomo?? ---
Od: Guillaume Lelarge [mailto: guilla...@lelarge.info]
Wys?ane: Monday, January 30, 2012 05:17 PM
Do: bdmyt...@eranet.pl
Kopia: pgadmin-suppo
On Mon, 2012-01-30 at 13:13 +0100, bdmyt...@eranet.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 doin
January 26, 2012 10:14 PM
Do: bdmyt...@eranet.pl
Kopia: pgadmin-support@postgresql.org
Temat: Re: [pgadmin-support] column level privilages error
On Thu, 2012-01-26 at 08:20 +0100, bdmyt...@eranet.pl wrote:
> Thanks,
> I manually edited table script (there was DEFAULT nextaval...) so
On Thu, 2012-01-26 at 08:20 +0100, bdmyt...@eranet.pl wrote:
> Thanks,
> I manually edited table script (there was DEFAULT nextaval...) so I
> missed last parenthesis - my fault.
> I agree pgAdmin shouldn't display all warnings, but I think some of
> them shouldn't be ignerd - like this one.
Well,
ds,
Bartek
--- Oryginalna wiadomo?? ---
Od: Guillaume Lelarge [mailto: guilla...@lelarge.info]
Wys?ane: Wednesday, January 25, 2012 11:11 PM
Do: bdmyt...@eranet.pl
Kopia: pgadmin-support@postgresql.org
Temat: Re: [pgadmin-support] column level privilages error
On Wed, 2012-01-25 at 13:01 +0
On Wed, 2012-01-25 at 13:01 +0100, bdmyt...@eranet.pl wrote:
> Hi,
> thanks for quick reply.
> application parameters:
> 1. pgAdmin 1.14.1 on Windows 7 Enterprise 32 bit
> 2. Server: PostgreSQL 9.1.2, compiled by Visual C++ build 1500, 64-bit on
> Windows Server 2008 R2 Standard
> scenario:
> 1. a
ssue a warning message if no grant options are
held, while the other forms will issue a warning if grant options for any of
the privileges specifically named in the command are not held. (In principle
these statements apply to the object owner as well, but since the owner is
always treated as holdi
On Thu, 2012-01-19 at 14:13 +0100, bdmyt...@eranet.pl wrote:
[...]
> I think, there is little bug in column privilage mechanism. The bug occures
> when You try to set column privilages using user name who has no rights to do
> this.
> For table there is no tab "Privilages", for columns it exists
HI all,
I think, there is little bug in column privilage mechanism. The bug occures
when You try to set column privilages using user name who has no rights to do
this.
For table there is no tab "Privilages", for columns it exists and accepts
configuration. Even when You accept Your configuration
10 matches
Mail list logo
