On 13 Jan 2015 22:18, "Zelaznik, Steve" <szelazni@aegonusa.com> wrote:
>
> I’m more explicit with my CASE statements, explicitly putting the equals sign in place. Such as in the attachment “explicit_equals.gif”. I’m not sure how your CASE statement works, but generally you can only omit the equals sign when you’re dealing with a pure Boolean value, such as the other attachment “pure_ bool.gif”.
>
I guess
Select case col1 when 1 then true when 0 then false end as int_as_bool from table1;
Should work as well (I need to try it out to be sure).
In you case anyways the columns is "pure boolean". So I guess you can skip converting to char in case statement.
>
>
> -Steve Z
>
>
>
> From: pgsql-novice-owner@postgresql.org [mailto:pgsql-novice-owner@postgresql.org] On Behalf Of Sameer Kumar
> Sent: Monday, January 12, 2015 1:31 AM
> To: JORGE MALDONADO
> Cc: pgsql-novice@postgresql.org
> Subject: Re: [NOVICE] Convert boolean field to a 0 or a 1 in a select statement
>
>
>
>
>
> On Sat, Jan 10, 2015 at 12:47 AM, JORGE MALDONADO <jorgemal1960@gmail.com> wrote:
>
> CAST(fce_subdivision as CHAR) AS fce_subdivision_aux,
>
> CASE CAST(fce_subdivision as CHAR)
>
> WHEN 'f' THEN '0'
>
> WHEN 't' THEN '1'
>
> END
>
>
>
> Why do you want to cast it first to char?
>
>
>
> And anyways what is the issue with casting it to number first and then casting it to char?
>
>
>
>
>
>
>
> Best Regards,
>
> Sameer Kumar | Database Consultant
>
> ASHNIK PTE. LTD.
>
> 101 Cecil Street, #11-11 Tong Eng Building, Singapore 069533
>
> M: +65 8110 0350 T: +65 6438 3504 | www.ashnik.com
>
>
>
>
>
> This email may contain confidential, privileged or copyright material and is solely for the use of the intended recipient(s).