Received: from mail.computalog.com ([209.82.103.230]) by postgresql.org (8.11.3/8.11.1) with ESMTP id f56GQ9E11035 for ; Wed, 6 Jun 2001 12:26:09 -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 KAA01087 for ; Wed, 6 Jun 2001 10:26:40 -0600 Received: from computalog.com (localhost [127.0.0.1]) by jamie.edmonton.computalog.com (Postfix) with ESMTP id 22FE7197399 for ; Wed, 6 Jun 2001 10:34:32 -0600 (MDT) Message-ID: <3B1E5B98.7A694F2@computalog.com> Date: Wed, 06 Jun 2001 10:34:32 -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: Cascade constraint gone!!! Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Archive-Number: 200106/70 X-Sequence-Number: 3288 Hi, I recently wipe my database away. And some of the tables have a UPDATE CASCADE on it to another table. When I reload the data from my backup that I did with pg_dumpall. My code started to give me an error because I tried to modify a table that was reference from another table. But the referenced table should have an UPDATE CASCADE. But according to the error it doesn't. Is there a way to add the ON UPDATE CASCADE back without dropping any table again? Thanks -- Linh Luong