X-Original-To: pgsql-sql-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by postgresql.org (Postfix) with ESMTP id 5F6809DC832 for ; Tue, 24 Jan 2006 12:08:34 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 35839-02 for ; Tue, 24 Jan 2006 12:08:32 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey- Received: from floppy.pyrenet.fr (news.pyrenet.fr [194.116.145.2]) by postgresql.org (Postfix) with ESMTP id DC6979DC82D for ; Tue, 24 Jan 2006 12:08:31 -0400 (AST) Received: by floppy.pyrenet.fr (Postfix, from userid 106) id 322B130EFE; Tue, 24 Jan 2006 17:08:31 +0100 (MET) From: "codeWarrior" X-Newsgroups: pgsql.sql Subject: Re: How to implement Microsoft Access boolean (YESNO) fieldtype in PostgreSQL ? Date: Tue, 24 Jan 2006 08:08:59 -0800 Organization: iDynaTECH, Inc. Lines: 32 Message-ID: References: <20060122211351.371f20d8@io.solnet> Reply-To: "codeWarrior" X-Complaints-To: usenet@news.hub.org X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2900.2180 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 X-RFC2646: Format=Flowed; Original To: pgsql-sql@postgresql.org X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0.783 required=5 tests=[AWL=0.234, FORGED_HOTMAIL_RCVD2=0.549] X-Spam-Score: 0.783 X-Spam-Level: X-Archive-Number: 200601/154 X-Sequence-Number: 23943 SELECT fieldlist, CASE WHEN myboolean = true THEN 1 ELSE 0 END FROM tblname WHERE condition; ""Jesper K. Pedersen"" wrote in message news:20060122211351.371f20d8@io.solnet... > > I am have some difficulties converting the Microsoft field of type > YESNO (which is a simple boolean true/false) to something that is > compatible with PostgreSQL. > > I have tried with both boolean, bit(1) and even integer to try and get > it to work but with no success - Access see the boolean and bit(1) as > "text" fields. > > This mean that I am not able to use the built-in form input fields for > the "YESNO" field type. > > Anyone with any ideas on how to get around this? > > Thank's > Jesper K. Pedersen > > ---------------------------(end of broadcast)--------------------------- > TIP 9: In versions below 8.0, the planner will ignore your desire to > choose an index scan if your joining column's datatypes do not > match >