Skip site navigation (1) Skip section navigation (2)

RE: currval() problem

From: Peter Mount <petermount(at)maidstone(dot)gov(dot)uk>
To: "'tony'" <tony(at)uickarate(dot)com>, pgsql-interfaces <pgsql-interfaces(at)postgresql(dot)org>
Subject: RE: currval() problem
Date: 2000-11-29 09:37:04
Message-ID: 1B3D5E532D18D311861A00600865478CF1B5E6@exchange1.nt.maidstone.gov.uk (view raw or flat)
Thread:
Lists: pgsql-interfaces
How are you accessing currval(). Can you post an example?

currval() is implemented in the backend, so there should be no difference
between how its returned and how any other value is returned, so it might be
how you are calling it thats not working.

Peter

-- 
Peter Mount
Enterprise Support Officer, Maidstone Borough Council
Email: petermount(at)maidstone(dot)gov(dot)uk
WWW: http://www.maidstone.gov.uk
All views expressed within this email are not the views of Maidstone Borough
Council


> -----Original Message-----
> From: tony [mailto:tony(at)uickarate(dot)com]
> Sent: Wednesday, November 29, 2000 1:16 AM
> To: pgsql-interfaces
> Subject: [INTERFACES] currval() problem
> 
> 
> Hello
> 
> I have a problem with currval() through JDBC.  
> My nextval() updates the counter of sequences, but
> currval() returns no value even after I call nextval().
> Both work fine when I try them through psql.  
> Have you encountered this problem before??
> 
> 
> Tony
> 

pgsql-interfaces by date

Next:From: Tibor LaszloDate: 2000-11-29 11:01:04
Subject: Re: slow odbc access....
Previous:From: Peter MountDate: 2000-11-29 09:35:08
Subject: RE: postgreSQL and javascript

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group