Received: from davinci.ethosmedia.com (davinci.ethosmedia.com [209.10.40.250]) by postgresql.org (8.11.3/8.11.1) with ESMTP id f3DG84863628 for ; Fri, 13 Apr 2001 12:08:04 -0400 (EDT) (envelope-from josh@agliodbs.com) Received: from [209.10.40.250] (account ) by davinci.ethosmedia.com (CommuniGate Pro WebUser 3.4.1) with HTTP id 37672 for ; Fri, 13 Apr 2001 09:08:03 -0700 From: "Josh Berkus" Subject: BOOLEAN data type? To: pgsql-sql@postgresql.org X-Mailer: CommuniGate Pro Web Mailer v.3.4.1 Date: Fri, 13 Apr 2001 09:08:03 -0700 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 8bit X-Archive-Number: 200104/202 X-Sequence-Number: 2552 Folks: I had assumed that the BOOL column type was a tru boolean. That is, I wrote some functions on the understand that, given table def: CREATE TABLE order_details ( order_detail_id SERIAL NOT NULL PRIMARY KEY, detail_id INT4 NOT NULL, order_usq INT4 NOT NULL, detail_required BOOL DEFAULT FALSE ); That the following query: SELECT detail_id FROM order_detials WHERE order_usq = 7703 AND detail_required; ... should be equivalent to: SELECT detail_id FROM order_detials WHERE order_usq = 7703 AND detail_required = TRUE; However, in testing (7.1 RC2), the query turned out to mean this: SELECT detail_id FROM order_detials WHERE order_usq = 7703 AND detail_required IS NOT NULL; ... throwing off a lot of my results until I figured it out. Can someone explain this to me? I thought the whole point of a BOOL data type was that it could be treated as a Boolean value, and used for testing and comparison without and "= TRUE" or "= FALSE". What's going on here? -Josh ______AGLIO DATABASE SOLUTIONS___________________________ Josh Berkus Complete information technology josh@agliodbs.com and data management solutions (415) 565-7293 for law firms, small businesses fax 621-2533 and non-profit organizations. San Francisco