X-Original-To: pgsql-sql@postgresql.org Received: from spampd.localdomain (postgresql.org [64.49.215.8]) by postgresql.org (Postfix) with ESMTP id 16494476182 for ; Tue, 6 May 2003 13:26:06 -0400 (EDT) Received: from web12708.mail.yahoo.com (web12708.mail.yahoo.com [216.136.173.245]) by postgresql.org (Postfix) with SMTP id 42203475E77 for ; Tue, 6 May 2003 13:26:05 -0400 (EDT) Message-ID: <20030506172604.92026.qmail@web12708.mail.yahoo.com> Received: from [207.188.167.123] by web12708.mail.yahoo.com via HTTP; Tue, 06 May 2003 10:26:04 PDT Date: Tue, 6 May 2003 10:26:04 -0700 (PDT) From: chester c young Subject: Re: UNIQUE boolean: only one row may be "true" To: Randall Lucas Cc: pgsql-sql@postgresql.org In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Spam-Status: No, hits=-9.5 required=5.0 tests=BAYES_20,IN_REP_TO,QUOTED_EMAIL_TEXT autolearn=ham version=2.50 X-Spam-Level: X-Spam-Checker-Version: SpamAssassin 2.50 (1.173-2003-02-20-exp) X-Archive-Number: 200305/95 X-Sequence-Number: 13260 > How shall I create a constraint such that only one row may be 'true'? Instead of, or along with your pg boolean, use a C type boolean where true is 1 and false is null: ... col_tf int check( col_tf = 1 || col_tf is null ) unique, ... a kludge to be sure, but works __________________________________ Do you Yahoo!? The New Yahoo! Search - Faster. Easier. Bingo. http://search.yahoo.com