Received: from gw.hcs.com.au (mail.hcs.com.au [203.12.235.237]) by mail.postgresql.org (8.11.1/8.11.1) with ESMTP id f0H21U050086 for ; Tue, 16 Jan 2001 21:01:32 -0500 (EST) (envelope-from keith@heart.com.au) Received: from tardis.hcs.com.au (IDENT:root@tardis.hcs.com.au [192.168.0.42]) by gw.hcs.com.au (8.9.3/8.9.3) with ESMTP id NAA17106 for ; Wed, 17 Jan 2001 13:18:02 +1100 Received: from heart.com.au ([192.168.0.65]) by tardis.hcs.com.au (8.9.3/8.8.7) with ESMTP id NAA29858 for ; Wed, 17 Jan 2001 13:01:24 +1100 Message-ID: <3A64FCEA.178112AF@heart.com.au> Date: Wed, 17 Jan 2001 13:01:14 +1100 From: Keith Gray X-Mailer: Mozilla 4.74 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: pgsql-sql@postgresql.org Subject: Boolean and Bit Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Archive-Number: 200101/179 X-Sequence-Number: 843 Hello All, This is my first post (so be gentle with me)... Is there a searchable archive? I would like suggestions and examples of adding SQL-92 data type BIT compatibility to a PostgreSQL schema. From the doc's I gather you can "CREATE TYPE bit" with storage int or int4... but I don't know about the input/output for zero and one. Should SQL (ODBC) be able to ask "WHERE bitfield;" or should it ask "WHERE bitfield = 1;" ? Any response gratefully recognized... Keith