From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | 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 15:17:09 |
Message-ID: | Pine.LNX.4.56.0307231714090.1649@krusty.credativ.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Tom Lane writes:
> Note that the spec only really speaks to the question of what booleans
> look like when written as constants in SQL statements. AFAICT it does
> not take a position on what representations are to be used when
> transferring data into or out of the database. So using '0' or '1' as
> input to a boolean field is not contrary to spec, but merely outside
> the spec (and in fact we will accept those strings for boolean...)
The transfer into the database is regulated when you write the data into
the SQL statement (as you normally would). Input through prepare/bind and
input is governed by the respective client interface (e.g., embedded SQL
language bindings, JDBC spec, ODBC spec). If you use libpq or psql then
you're beyond all standards anyway.
--
Peter Eisentraut peter_e(at)gmx(dot)net
From | Date | Subject | |
---|---|---|---|
Next Message | Bruno Wolff III | 2003-07-23 15:28:39 | Re: Question (or feature request) on serial datatype |
Previous Message | Claudio Lapidus | 2003-07-23 15:13:19 | 7.4dev or beta version |