Re: [HACKERS] ODBC driver flakieness - Mailing list pgsql-odbc

From Hiroshi Inoue
Subject Re: [HACKERS] ODBC driver flakieness
Date
Msg-id 3BB111A3.D77C7F11@tpf.co.jp
Whole thread Raw
In response to Re: [HACKERS] ODBC driver flakieness  ("Gowey, Geoffrey" <ggowey@rxhope.com>)
List 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

pgsql-odbc by date:

Previous
From: Dave Page
Date:
Subject: Re: [HACKERS] UTF-8 support
Next
From: Jim Hines
Date:
Subject: Re: dynasets