Received: from localhost (maia-4.hub.org [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id 277919FA0FB for ; Thu, 14 Dec 2006 10:14:09 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-new, port 10024) with ESMTP id 82601-02 for ; Thu, 14 Dec 2006 10:14:02 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 Received: from coe.tamu.edu (edsun.coe.tamu.edu [165.91.232.6]) by postgresql.org (Postfix) with ESMTP id E95E89F9FDA for ; Thu, 14 Dec 2006 10:13:58 -0400 (AST) Received: (from root@localhost) by coe.tamu.edu (8.11.7p2+Sun/8.12.11) id kBEEBIT26037 for pgsql-admin@postgresql.org; Thu, 14 Dec 2006 08:11:18 -0600 (CST) Received: from coe.tamu.edu (coe.tamu.edu [165.91.232.6]) by coe.tamu.edu (8.11.7p2+Sun/8.12.11) with ESMTP id kBEEAEC26001; Thu, 14 Dec 2006 08:10:14 -0600 (CST) Date: Thu, 14 Dec 2006 08:10:14 -0600 (CST) From: "Ben K." To: Jerry Sievers cc: pgsql-admin@postgresql.org Subject: Re: How to enforce the use of the sequence for serial columns In-Reply-To: Message-ID: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Virus-Scanned: by AMaViS 0.3.12 X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200612/203 X-Sequence-Number: 23995 > It's not a full solution anyway since it prevents any kind of update > on the table due to check constraints firing even if target field not > updated. See below; Right. It was not a valid idea ... Regards, Ben K. Developer http://benix.tamu.edu