Re: 0/1 vs true/false

I ran into this problem some time ago. I ended up using a query with a
CASE statement in it to caste the boolean as a 1 or 0. I guess one could
do this as a view as well.

Jean-Christian Imbeault wrote:

> Just having a small argument with an application developer ...
>
> is using 0/1 for boolean types SQL compliant? I am trying to convince
> him that the proper SQL compliant (and postgresql compliant) syntax is
> true/false but he won't budge ...
>
> The app as currently written no longer works with postgres because
> they code uses 0/1 instead of the now enforced true/false for boolean
> types.
>
> Can someone point me to an SQL spec and section where this is clearly
> stated out?
>
> Thanks,
>
> Jean-Christian Imbeault
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 3: if posting/reading through Usenet, please send an appropriate
> subscribe-nomail command to majordomo@postgresql.org so that your
> message can get through to the mailing list cleanly
>
>