Received: from mailout00.sul.t-online.com (mailout00.sul.t-online.com [194.25.134.16]) by hub.org (8.9.3/8.9.3) with ESMTP id QAA82985 for ; Fri, 2 Jun 2000 16:45:21 -0400 (EDT) (envelope-from JanWieck@t-online.de) Received: from fwd06.sul.t-online.de by mailout00.sul.t-online.com with smtp id 12xyJj-0007Pf-02; Fri, 2 Jun 2000 22:45:19 +0200 Received: from hot.jw.home (340000654369-0001@[62.224.102.188]) by fwd06.sul.t-online.de with esmtp id 12xyJV-0deLEOC; Fri, 2 Jun 2000 22:45:05 +0200 Received: (from wieck@localhost) by hot.jw.home (8.8.5/8.8.5) id VAA07464; Fri, 2 Jun 2000 21:14:56 +0200 From: JanWieck@t-online.de (Jan Wieck) Message-Id: <200006021914.VAA07464@hot.jw.home> Subject: Re: Deferral of primary key constraint In-Reply-To: <3937D411.7B47A641@actarg.com> from Kyle Bateman at "Jun 2, 2000 09:34:42 am" To: Kyle Bateman Date: Fri, 2 Jun 2000 21:14:56 +0200 (MEST) CC: pgsql-sql@postgresql.org Reply-To: Jan Wieck X-Mailer: ELM [version 2.4ME+ PL68 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Sender: 340000654369-0001@t-dialin.net X-Archive-Number: 200006/22 Kyle Bateman wrote: > Is it possible to defer the check on a primary key constraint (or a > check constraint, for that matter). Here is an example that shows why > it would be nice to be able to do so. We have a real-life scenario that > is similar (but much more complex). Not yet. Only the trigger based foreign key checks are deferrable in 7.0. We discovered the need for deferrability of UNIQUE (what is what you want from the PK things) and other checks. Not sure up to now how we could do it, but a known problem. Jan -- #======================================================================# # It's easier to get forgiveness for being wrong than for being right. # # Let's break this rule - forgive me. # #================================================== JanWieck@Yahoo.com #