| From: | "scott(dot)marlowe" <scott(dot)marlowe(at)ihs(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Jean-Christian Imbeault <jc(at)mega-bucks(dot)co(dot)jp>, Peter Eisentraut <peter_e(at)gmx(dot)net>, <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: 0/1 vs true/false |
| Date: | 2003-07-23 16:02:46 |
| Message-ID: | Pine.LNX.4.33.0307230959390.21905-100000@css120.ihs.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Wed, 23 Jul 2003, Tom Lane wrote:
> Jean-Christian Imbeault <jc(at)mega-bucks(dot)co(dot)jp> writes:
> > Oops, I meant to say can someone point me to a ressource (SQL standard
> > and section?) which states that true/false must be used for booleans :)
>
> Well, there is no boolean type per se in SQL92. But there is in SQL99.
> I think the most relevant part of the spec is the definition of boolean
> literals in section 5.3:
>
> <boolean literal> ::=
> TRUE
> | FALSE
> | UNKNOWN
Was it pulled from SQL92 before it went standard? My copy of the
pre-release lists a boolean type, just like the 99 standard does.
further, intermediate SQL compliance has this in it:
24)Subclause 8.12, "<search condition>":
a) A <boolean test> shall not specify a <truth value>.
Does that mean you should only use the "is true" suntax, not the =true?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Errol Neal | 2003-07-23 16:05:54 | Re: Increasing Max # of connections |
| Previous Message | Karsten Hilbert | 2003-07-23 15:56:33 | Re: How do I manage PDF file |