From: | Hiroshi Inoue <Inoue(at)tpf(dot)co(dot)jp> |
---|---|
To: | "Gowey, Geoffrey" <ggowey(at)rxhope(dot)com> |
Cc: | pgsql-odbc(at)postgresql(dot)org |
Subject: | Re: [HACKERS] ODBC driver flakieness |
Date: | 2001-09-25 23:22:11 |
Message-ID: | 3BB111A3.D77C7F11@tpf.co.jp |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-odbc |
"Gowey, Geoffrey" wrote:
>
> RS] ODBC driver flakieness
> >
> >
> > Hi Gowey,
> > Please post to pgsql-odbc list if the problem is ODBC
> > specific.
> >
> > "Gowey, Geoffrey" wrote:
> > >
> > > Second problem: I create a table with a serial column. This
> > table is not in
> > > the existing db and no values are being set. The job bombs
> > when executed
> > > with a "you don't have permissions to set sequence ..._seq"
> > (why this is
> > > being modified at all I do not know).
> >
> > Is this an ODBC problem ?
> > If the e.g. inserting user is different from the one who created
> > the table, UPDATE permission on the sequence should be granted
> > as well.
>
> I don't know. The table does not exist at all in the db that I'm migrating
> from (so why it's being touched at all I don't know). Also, I created the
> column with one user and am importing the table with another user as the
> odbc login, but that whole table is rwx for that user. Did I miss
> something?
Tables and sequences are independent objects and
the permissions should be granted separately.
You seem to have to grant a rwx permission on
the sequence as well.
regards,
Hiroshi Inoue
From | Date | Subject | |
---|---|---|---|
Next Message | Jim Hines | 2001-09-26 12:24:00 | Re: dynasets |
Previous Message | Dave Page | 2001-09-25 19:43:09 | Re: [HACKERS] UTF-8 support |