| From: | "John Duffy" <jbduffy(at)ntlworld(dot)com> |
|---|---|
| To: | <pgsql-sql(at)postgresql(dot)org> |
| Subject: | NOTICE: generated by sequence nextval() |
| Date: | 2002-10-10 15:17:40 |
| Message-ID: | 001101c27070$3060bf10$9d88fc3e@desktop |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-sql |
Postgresql 7.1.3-2
Red Hat 7.2
I've noticed that if I create a sequence, and then do a select on it using nextval() everything works fine. However, if I drop the sequence and then create it again, the same select statement generates a NOTICE.
Is this normal behaviour or a bug? See below.
test=> create sequence serial;
CREATE
test=> select nextval('serial');
nextval
---------
1
(1 row)
test=> drop sequence serial;
DROP
test=> create sequence serial;
CREATE
test=> select nextval('serial');
NOTICE: serial.nextval: sequence was re-created
nextval
---------
1
(1 row)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Roberto Mello | 2002-10-10 15:19:59 | Re: SELECT with INNER data bases |
| Previous Message | Shridhar Daithankar | 2002-10-10 13:49:11 | Re: contrib/fixchar (Was: Large databases, performance) |