Re: 0/1 vs true/false - Mailing list pgsql-general

From Jean-Christian Imbeault
Subject Re: 0/1 vs true/false
Date
Msg-id 3F1E407B.40401@mega-bucks.co.jp
Whole thread Raw
In response to Re: 0/1 vs true/false  ("Nigel J. Andrews" <nandrews@investsystems.co.uk>)
Responses Re: 0/1 vs true/false  (Dennis Gearon <gearond@cvc.net>)
List pgsql-general
Nigel J. Andrews wrote:
>
> I had do do this sort of thing for a some developers. It was actually 'true'
> and 'false' that was wanted not the 0/1. I wrote a little plgsql function and
> installed it as a cast to text.

Thanks. I know that there are workarounds, I just want to "prove" that
0/1 is not standards compliant. If I can do that I am pretty sure that
the developer will have nothing against changing to true/false.

Right not he just things postgresql must be broken because 0/1 works in
MySQL ... But he's pretty good when it comes to fixing things because
they don't follow standards. So if I can show him his SQL isn't
standards compliant he'll probably happily fix it.

Jean-Christian Imbeault


pgsql-general by date:

Previous
From: "Nigel J. Andrews"
Date:
Subject: Re: 0/1 vs true/false
Next
From: Kaarel
Date:
Subject: Re: dump_all/restore times?