Received: from mx99.openu.ac.il (arbel.openu.ac.il [147.233.32.4]) by hub.org (8.9.3/8.9.3) with ESMTP id FAA97768 for ; Wed, 14 Jul 1999 05:43:19 -0400 (EDT) (envelope-from herouth@oumail.openu.ac.il) Received: from talmon.openu.ac.il (talmon.openu.ac.il [147.233.32.11]) by mx99.openu.ac.il (Postfix) with ESMTP for id F3E4B4B638; Wed, 14 Jul 1999 12:43:17 +0300 (IDT) Received: from [147.233.159.109] (mac-herouth.pc.openu.ac.il) by talmon.openu.ac.il (Netscape Messaging Server 3.54) with ESMTP id AAA1ACD; Wed, 14 Jul 1999 12:46:26 +0300 X-Sender: herouth@shaked.cc.openu.ac.il Message-Id: In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Wed, 14 Jul 1999 12:43:32 +0300 To: Michael Richards , pgsql-sql@postgreSQL.org From: Herouth Maoz Subject: Re: [SQL] counting bools in a complex query At 02:31 +0300 on 14/07/1999, Michael Richards wrote: > My final problem is to count all the messages with flagnew set to true. > The only way I can think to do this is to convert the bool value to a 1 or > 0 (which I think should be a standard conversion anyway) and run a sum() > on them. > > Unless anyone can come up with a better way to do this, What is the best > way to implement a conversion from bool to int? Depends on your version. If you have 6.5, you can probably use COALESCE or CASE. In previous versions, I would define an SQL function. The first one that comes to mind would be: CREATE FUNCTION to_int( bool ) RETURNS int4 AS 'SELECT 1 WHERE $1 UNION SELECT 0 WHERE NOT $1'; Another approach would be the following: CREATE FUNCTION only_true( bool ) RETURNS bool AS 'SELECT $1 WHERE $1 IS NOT NULL AND $1'; This would return true when the argument is true, null in all other cases. You can use this with count rather than sum. Of course, you could decide that you would fill the flagnew with either true or null, instead of true and false. If you do, you could do a count without the above function. You could get the true/false by asking whethe flagnew IS NOT NULL. Finally, the UNION is the way to go when you want to implement an outer join, but using NOT IN is not recommended, because it is inefficient. A better subquery would be: NOT EXIST ( SELECT * FROM usermail WHERE loginid='michael' AND folder = folderid ) Herouth -- Herouth Maoz, Internet developer. Open University of Israel - Telem project http://telem.openu.ac.il/~herutma