RE: [INTERFACES] sequences

From: Herouth Maoz <herouth(at)oumail(dot)openu(dot)ac(dot)il>
To: "Jackson, DeJuan" <djackson(at)cpsgroup(dot)com>, prlw1(at)cam(dot)ac(dot)uk, pgsql-interfaces(at)postgreSQL(dot)org
Subject: RE: [INTERFACES] sequences
Date: 1999-05-03 11:57:54
Message-ID: l03130303b3533f15686c@[147.233.159.109]
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-interfaces

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.

Herouth

--
Herouth Maoz, Internet developer.
Open University of Israel - Telem project
http://telem.openu.ac.il/~herutma

In response to

Responses

Browse pgsql-interfaces by date

  From Date Subject
Next Message Mario Simeone 1999-05-03 16:19:32 Bug reporting...
Previous Message Bobby Mitchell 1999-05-03 11:13:44 (no subject)