| From: | Jean-Michel POURE <jm(dot)poure(at)freesurf(dot)fr> | 
|---|---|
| To: | pgsql-general(at)postgresql(dot)org | 
| Cc: | pgadmin-hackers(at)postgresql(dot)org | 
| Subject: | Re: [GENERAL] Use of Serial Datatype and Sequence Issue | 
| Date: | 2001-11-06 07:58:40 | 
| Message-ID: | 4.2.0.58.20011106085417.00a987b0@pop.freesurf.fr | 
| Views: | Whole Thread | Raw Message | Download mbox | Resend email | 
| Thread: | |
| Lists: | pgadmin-hackers pgsql-general | 
At 00:28 02/11/01 +0000, you wrote:
>I am new to postgres and am in the process of creating a new database of
>several 100 tables.  Most of the tables have a serial datatype. When the
>table is created psql says it is creating an implicit sequence.  Yet
>when I drop the table and even when I drop the database the sequence is
>still there. When I try to re-create the table it fails beacuse the
>sequence already exists.  This same behaviour exists for indexes.  How
>can I get rid of any sequences or indexes that have been created.  I
>would prefer not to explicitly drop each one.  Ideally I would like to
>drop the table and have all related indexes, sequences dropped.
pgAdmin2 knows how to drop indexes when dropping a table: 
http://pgadmin.postgresql.org
It might not be interesting to drop a sequence as it can be used by 
multiple tables.
Dave: do you think pgAdmin2 should drop a sequence when dropping a table?
Best regards,
Jean-Michel POURE
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dave Page | 2001-11-06 08:17:05 | Re: [GENERAL] Use of Serial Datatype and Sequen | 
| Previous Message | Keary Suska | 2001-11-06 06:42:51 | Re: Use of Serial Datatype and Sequence Issue | 
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jean-Michel POURE | 2001-11-06 08:02:06 | Re: functions, shell script | 
| Previous Message | Jean-Michel POURE | 2001-11-06 07:52:35 | Re: Referring a table in another database |