| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Franco Bruno Borghesi <franco(at)akyasociados(dot)com(dot)ar> |
| Cc: | Jochem van Dieten <jochemd(at)oli(dot)tudelft(dot)nl>, Jean-Christian Imbeault <jc(at)mega-bucks(dot)co(dot)jp>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: 0/1 vs true/false |
| Date: | 2003-07-23 14:48:59 |
| Message-ID: | 13020.1058971739@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Franco Bruno Borghesi <franco(at)akyasociados(dot)com(dot)ar> writes:
> This makes me wonder, what about 't' and 'f'?... will they disappear in
> newer versions of postgreSQL?
No. See my comment about I/O representations being outside the spec.
There is no inconsistency in the following examples:
regression=# select true;
bool
------
t
(1 row)
regression=# select t;
ERROR: attribute "t" not found
regression=# select 't'::boolean;
bool
------
t
(1 row)
regression=# select '1'::boolean;
bool
------
t
(1 row)
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stephan Szabo | 2003-07-23 14:49:12 | Re: Performance hit of foreign key constraints? |
| Previous Message | Tom Lane | 2003-07-23 14:43:31 | Re: 0/1 vs true/false |