Re: Fw: Removing foreign key and adding sequence - Mailing list pgsql-novice

From Chad Thompson
Subject Re: Fw: Removing foreign key and adding sequence
Date
Msg-id 007201c33cc1$15f37fa0$32021aac@chad
Whole thread Raw
In response to Fw: Removing foreign key and adding sequence  ("Chad Thompson" <chad@weblinkservices.com>)
Responses Re: Fw: Removing foreign key and adding sequence
List pgsql-novice
 drop trigger "RI_ConstraintTrigger_10337860" on lists;

worked perfectly! Thanks

How come I have to do the 7.2 method when I have 7.3?

select version();
                                                 version
----------------------------------------------------------------------------
-----------------------------
 PostgreSQL 7.3.2 on i686-pc-linux-gnu, compiled by GCC gcc (GCC) 3.2
20020903 (Red Hat Linux 8.0 3.2-7)
(1 row)

Thanks
Chad

----- Original Message -----
From: "Nabil Sayegh" <postgresql@e-trolley.de>
To: "Chad Thompson" <chad@weblinkservices.com>
Cc: "pgsql-novice" <pgsql-novice@postgresql.org>
Sent: Thursday, June 26, 2003 3:27 PM
Subject: Re: Fw: [NOVICE] Removing foreign key and adding sequence


> Am Don, 2003-06-26 um 23.19 schrieb Chad Thompson:
> > > >  7.32.  Can I just drop the foreign key?  That would be SO much
easier
> > :-)
> > >
> > > Since 7.3 it's very easy, but even with 7.2 you could:
> > >
> > > 7.3:
> > > \d table_name
> > > if the key is labeled with e.g. $1:
> > > ALTER TABLE table_name DROP CONSTRAINT "$1";
> > > >
> >
> > Hrm... What could I be doing wrong?
>
> Your FK are 7.2 style (actually they are < 7.3)
> (they are triggers)
>
> > Triggers: RI_ConstraintTrigger_10337839,
> >           RI_ConstraintTrigger_10337842,
> >           RI_ConstraintTrigger_10337860
>
> Just take the example from 7.2
>
> HTH
> --
>  e-Trolley Sayegh & John, Nabil Sayegh
>  Tel.: 0700 etrolley /// 0700 38765539
>  Fax.: +49 69 8299381-8
>  PGP : http://www.e-trolley.de
>
>


pgsql-novice by date:

Previous
From: Tom Lane
Date:
Subject: Re: authentication questions
Next
From: Josh Berkus
Date:
Subject: Re: SELECT too complex?