| From: | Jean-Christian Imbeault <jc(at)mega-bucks(dot)co(dot)jp> |
|---|---|
| To: | "Nigel J(dot) Andrews" <nandrews(at)investsystems(dot)co(dot)uk> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: 0/1 vs true/false |
| Date: | 2003-07-23 07:59:55 |
| Message-ID: | 3F1E407B.40401@mega-bucks.co.jp |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kaarel | 2003-07-23 08:24:59 | Re: dump_all/restore times? |
| Previous Message | Nigel J. Andrews | 2003-07-23 07:57:52 | Re: 0/1 vs true/false |