I haven't been able to recreate any of this???
When a table is made, it automatically is owned by the owner of the
connection, so it should have write privleges by the owner???
I did note that oo defaults to trying to use the connection owners name
for schema, I forced it to public when I created my tables. Does that
make a difference ?
I did find one more thing though
oo tries to create index's using the following syntax; which won't work
CREATE INDEX "id_idx" ON "public"."ootable" ( "id" DESC)
Dave
On Wed, 2003-03-19 at 04:36, Dave Cramer wrote:
> 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@attbi.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@postgresql.org
--
Dave Cramer <Dave@micro-automation.net>
