Re: currval and nextval in 7.3.4 - Mailing list pgsql-bugs

From j6m@adm.estp.fr
Subject Re: currval and nextval in 7.3.4
Date
Msg-id 1066942162.3f983ed25cc87@213.244.11.231
Whole thread Raw
In response to currval and nextval in 7.3.4  (Keith Marr <marrk@comcast.net>)
List pgsql-bugs
Hello,

Quoting Keith Marr <marrk@comcast.net>:

> Hi,
>
> I recently installed 7.3.4 (complete install from scratch) and both 'select
>
> nextval('my_seq') from my_table' and 'select currval('my_seq') from my_table'
>
> return a number of rows equal to the number of rows in the table.
>
> The sequence was created with a SERIAL type if that helps.
>  In 'psql' the results look like this.
>

I think "select nextval('my_seq');" is what you want to do.

> my_db=# select nextval('my_seq') from my_table;
>  nextval
> ---------
>        6
>        7
>        8
>        9
> (4 rows)
>

Idem with select currval('my_seq');

> my_db=# select currval('my_seq') from my_table;
>  currval
> ---------
>        9
>        9
>        9
>        9
> (4 rows)
>
> I get the same results using the JDBC driver so it's not a psql problem.
>
> Any thoughts out there?
>
>

It is not a bug (or undocumented feature as some software vendor would say).
Your queries are syntaxically correct SQL requests, but they are not what you
really want.

(If you try "select now() from my_table;", it will also return 4 rows.)

Regards
J6M

pgsql-bugs by date:

Previous
From: Josh Wilmes
Date:
Subject: ISM shared memory on solaris
Next
From: Bruce Momjian
Date:
Subject: Re: ISM shared memory on solaris