Re: Bug #581: Sequence cannot be deleted

From: Stephan Szabo <sszabo(at)megazone23(dot)bigpanda(dot)com>
To: <nbazin(at)ingenico(dot)com(dot)au>, <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: Bug #581: Sequence cannot be deleted
Date: 2002-02-12 02:14:31
Message-ID: 20020211181307.P86553-100000@megazone23.bigpanda.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-hackers


On Mon, 11 Feb 2002 pgsql-bugs(at)postgresql(dot)org wrote:

> BAZIN Nicolas (nbazin(at)ingenico(dot)com(dot)au) reports a bug with a severity of 1
> The lower the number the more severe it is.
>
> Short Description
> Sequence cannot be deleted
>
> Long Description A Sequence is created automatically with the SQL
> command:

> CREATE TABLE fa_ccpsholderscpt(hsc_serial SERIAL NOT NULL ,chd_serial
> INTEGER NOT NULL ,hsc_respcode CHAR(2) NOT NULL ,scp_code CHAR(4) NOT
> NULL ,imp_flag SMALLINT)
>
> but when I try to delete it with the following command:
> DROP SEQUENCE fa_ccpsholderscpt_hsc_serial_seq

That's not the name of the sequence in question unless you've upped
the number of characters in an identifier. The sequence appears to
on my machine be named "fa_ccpsholderscp_hsc_serial_seq" because the
name would have ended up being too long.

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2002-02-12 02:17:19 Re: Bug #581: Sequence cannot be deleted
Previous Message pgsql-bugs 2002-02-12 01:38:43 Bug #582: no mapping for java.sql.Types.DECIMAL

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2002-02-12 02:15:12 Re: Optimizer(?) off by factor of 3 ... ?
Previous Message pgsql-bugs 2002-02-12 01:26:37 Bug #581: Sequence cannot be deleted