Received: from as.tksoft.com (gyw.com [209.55.67.177] (may be forged)) by hub.org (8.9.3/8.9.3) with ESMTP id TAA26437 for ; Sat, 12 Feb 2000 19:36:17 -0500 (EST) (envelope-from tjk@tksoft.com) Received: (from tjk@tksoft.com) by uno.tksoft.com (8.8.8/8.8.8) id QAA16446; Sat, 12 Feb 2000 16:31:26 -0800 From: "tjk@tksoft.com" Message-Id: <200002130031.QAA16446@uno.tksoft.com> Subject: Re: [SQL] Type casting bool? To: phil@Stimpy.netroedge.com Date: Sat, 12 Feb 2000 16:31:25 -0800 (PST) Cc: pgsql-sql@hub.org In-Reply-To: <20000211202906.E19246@Stimpy.netroedge.com> from "phil@Stimpy.netroedge.com" at Feb 11, 0 08:29:06 pm Content-Type: text If you are using Postgres 6.5 +, you can use select case when mybool then 1 else 0 end from mytable; Of course, this would not, explicitly, take into consideration null fields. Troy > > > This seems like it would be simple, but I'm having troubles getting it > to work. All I wish to do is have Postgresql return '0' or '1' > instead of 'f' or 't' for bool types. This would simplify life for me > since I'm trying to dump these values right into expressions outside > of the context of SQL. Right now my parsers are choking on the 't's > and 'f's from PostgreSQL. > > I've tried: > > select mybool::int4; > > But, I get, > > ERROR: function int4(bool) does not exist > > Hummm.... I want to do something like: > > select (mybool?1:0); > > But, that's not the right syntax. I'd love to be able to get this > working w/o defining new functions or types (i.e., make it portable). > > Ideas? I've poured over the documentation and the current function > and operators, but this doesn't seem to be implemented?! > > Thanks! > > > Phil > > -- > Philip Edelbrock -- IS Manager -- Edge Design, Corvallis, OR > phil@netroedge.com -- http://www.netroedge.com/~phil > PGP F16: 01 D2 FD 01 B5 46 F4 F0 3A 8B 9D 7E 14 7F FB 7A > > ************ > >