En un mensaje anterior, Merlin Moncure escribió:
> On Tue, May 13, 2008 at 8:50 AM, Fernando Schapachnik
> <fernando@mecon.gov.ar> wrote:
> > > > ALTER SEQUENCE name [ INCREMENT [ BY ] increment ]
> > > > [ MINVALUE minvalue | NO MINVALUE ] [ MAXVALUE maxvalue | NO
> > > > MAXVALUE ]
> > > > [ RESTART [ WITH ] start ] [ CACHE cache ] [ [ NO ] CYCLE ]
> > >
> > > oop, you are using 8.1 :-). This was added in a later version. drop
> > > sequence ... cascade should probably work. you can try it out in a
> > > transaction to be sure.
> >
> > Thanks for your help, but cascade doesn't make a difference.
>
> What do you mean? PostgreSQL 8.1 has 'drop sequence cascade':
> http://www.postgresql.org/docs/8.1/i...psequence.html
>
> If this isn't working, can you paste the text of the error message?

Sorry I wasn't clear. I mean to say that the error message is the same
with or without cascade:

sso=# drop SEQUENCE table1_id_seq cascade;
ERROR: cannot drop sequence table1_id_seq because table
ambitos column id requires it
HINT: You may drop table table1 column id instead.

Thanks.

Fernando.

--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general