From: | Dave Cramer <Dave(at)micro-automation(dot)net> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | aklaver(at)attbi(dot)com, "pgsql-jdbc(at)postgresql(dot)org" <pgsql-jdbc(at)postgresql(dot)org> |
Subject: | Re: Follow-up OpenOffice and Postgres 7.3.2 |
Date: | 2003-03-19 09:36:00 |
Message-ID: | 1048066560.18393.119.camel@inspiron.cramers |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-jdbc |
The driver doesn't do anything when a "create table foo ..." is
executed, and there is no api for modifying the user permissions ??
Dave
On Wed, 2003-03-19 at 00:53, Tom Lane wrote:
> Adrian Klaver <aklaver(at)attbi(dot)com> writes:
> > I finally tracked down the problem. You have to use the GRANT command to set
> > privileges on your table. Postgres assumes the table owner has all rights but
> > does do not write that info into the access control list of pg_class. It
> > would seem the JDBC driver looks to pg_class for information on permissions.
>
> Hm. The backend treats NULL in pg_class.relacl as meaning the default
> permissions (owner = all, everyone else = none). I wonder whether jdbc
> gets that right?
>
> regards, tom lane
>
> ---------------------------(end of broadcast)---------------------------
> TIP 1: subscribe and unsubscribe commands go to majordomo(at)postgresql(dot)org
--
Dave Cramer <Dave(at)micro-automation(dot)net>
From | Date | Subject | |
---|---|---|---|
Next Message | Dave Cramer | 2003-03-19 09:40:57 | Re: auto generated keys |
Previous Message | Davide Romanini | 2003-03-19 09:35:08 | JDBC driver, PGSQL 7.3.2 and accents characters |