Received: from mail.computalog.com ([209.82.103.230]) by postgresql.org (8.11.3/8.11.1) with ESMTP id f57FmgE77076 for ; Thu, 7 Jun 2001 11:48:43 -0400 (EDT) (envelope-from linh.luong@computalog.com) Received: from jamie.edmonton.computalog.com (mugeri.computalog.com [209.82.103.229]) by mail.computalog.com (8.8.8/8.8.8) with ESMTP id IAA01591 for ; Thu, 7 Jun 2001 08:47:50 -0600 Received: from computalog.com (localhost [127.0.0.1]) by jamie.edmonton.computalog.com (Postfix) with ESMTP id 34C9B197399 for ; Thu, 7 Jun 2001 09:32:05 -0600 (MDT) Message-ID: <3B1F9E74.47067EEF@computalog.com> Date: Thu, 07 Jun 2001 09:32:04 -0600 From: Linh Luong X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.4.2-pentiumiii-smp i686) X-Accept-Language: en MIME-Version: 1.0 To: pgsql-sql@postgresql.org Subject: dropping constraints Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Archive-Number: 200106/103 X-Sequence-Number: 3322 Hi, Is there to drop a constraint when you add it separately with an alter statement. alter table failuretypecategory1 add constraint fk_failuretypecategory1 FOREIGN KEY (failurecategory1id) REFERENCES failurecategory1 (id) ON UPDATE CASCADE ON DELETE CASCADE; I tried drop trigger on failurecategory1 and drop trigger on failuretypecategory1 and also drop trigger on failurecategory1 and drop trigger on failuretypecategory1 But it kept saying ERROR: DropTrigger: there is no trigger / on relation failuretypecategory1 What am I doing wrong. I tried dropping the table also and when I tried to delete from a table that it referenced above it gave the error that the table I just drop doesn't exist. Obviously because I just removed it but the constraint it still there.. Thanks -- Linh Luong