From: | "Patrick Welche" <prlw1(at)newn(dot)cam(dot)ac(dot)uk> |
---|---|
To: | herouth(at)oumail(dot)openu(dot)ac(dot)il (Herouth Maoz) |
Cc: | pgsql-interfaces(at)postgresql(dot)org |
Subject: | Re: [INTERFACES] sequences |
Date: | 1999-05-04 16:11:30 |
Message-ID: | E10ehn8-0004bs-00@quartz.newn.cam.ac.uk |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-interfaces |
Herouth Maoz wrote:
>
> At 22:41 +0300 on 29/04/1999, Jackson, DeJuan wrote:
>
>
> > You might try placing the INSERT and SELECT CURRVAL into a transaction
> > block.
>
> That shouldn't make a difference. Currval's scope is the entire session,
> from the last call (or implicit call) to nextval to the next call.
>
> Now, let's see if I understand right: The query works well in psql, but not
> in a program? So let me ask you this - do you run the program, perhaps, as
> a different user, such as the httpd or nobody user? If so, you need to
> GRANT SELECT on the sequence to be able to use the currval function.
Thank you!! That was it. (I had granted access to tables, not to sequences)
Cheers,
Patrick
From | Date | Subject | |
---|---|---|---|
Next Message | JT Kirkpatrick | 1999-05-04 16:42:03 | is the odbc driver or me inconsistent?? |
Previous Message | JT Kirkpatrick | 1999-05-04 15:37:22 | RE: [INTERFACES] error message |