From: | "tjk(at)tksoft(dot)com" <tjk(at)tksoft(dot)com> |
---|---|
To: | phil(at)Stimpy(dot)netroedge(dot)com |
Cc: | pgsql-sql(at)hub(dot)org |
Subject: | Re: [SQL] Type casting bool? |
Date: | 2000-02-13 00:31:25 |
Message-ID: | 200002130031.QAA16446@uno.tksoft.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-sql |
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(at)netroedge(dot)com -- http://www.netroedge.com/~phil
> PGP F16: 01 D2 FD 01 B5 46 F4 F0 3A 8B 9D 7E 14 7F FB 7A
>
> ************
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2000-02-13 06:36:09 | Re: [SQL] Type casting bool? |
Previous Message | Peter Stamfest | 2000-02-12 23:57:04 | text -> char |