From: | "Chris Mair" <chris(at)1006(dot)org> |
---|---|
To: | pgsql-bugs(at)postgresql(dot)org |
Subject: | BUG #2336: will not drop implicitly created sequence |
Date: | 2006-03-19 20:43:50 |
Message-ID: | 200603192043.k2JKho1n047098@wwwmaster.postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
The following bug has been logged online:
Bug reference: 2336
Logged by: Chris Mair
Email address: chris(at)1006(dot)org
PostgreSQL version: 8.1.3
Operating system: MacOS X 10.3.9
Description: will not drop implicitly created sequence
Details:
Ok, so this is probably not a bug at all - just slightly unexpected
behaviour.
This piece of SQL:
---------------------------------------------------
create table test2 (id serial, txt varchar);
-- (will create implicit sequence "test2_id_seq")
alter table test2 alter id set default 123;
drop sequence test2_id_seq;
---------------------------------------------------
would say:
---------------------------------------------------
ERROR: 2BP01: cannot drop sequence test2_id_seq because table test2 column
id requires it
HINT: You may drop table test2 column id instead.
LOCATION: recursiveDeletion, dependency.c:472
---------------------------------------------------
as if test2.id would still use the sequence.
Contrast this with the same thing done with an explicitly declared
sequence:
---------------------------------------------------
create sequence test1_id_seq;
create table test1 (id int not null default nextval('test1_id_seq'), txt
varchar);
alter table test1 alter id set default 123;
drop sequence test1_id_seq;
---------------------------------------------------
which will just work fine.
From | Date | Subject | |
---|---|---|---|
Next Message | rama krishna | 2006-03-20 07:38:39 | BUG #2337: database connection |
Previous Message | Michael Meskes | 2006-03-19 12:33:05 | Re: BUG #2330: ECPGlib: Wrong error code in case of a duplicate key violation |