From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
---|---|
To: | Andreas 'ads' Scherbaum <adsmail(at)wars-nicht(dot)de> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Binary data type with other output method |
Date: | 2007-12-27 16:39:29 |
Message-ID: | 4773D541.9000808@dunslane.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Andreas 'ads' Scherbaum wrote:
>>> i considered this one but this would only bring 0/1 as input, not as
>>> output values, which is what i want.
>>>
>> er, what? This domain would have input and output values of 0/1.
>>
>
> Yes, but i will loose 't', 'true', 'f' and 'false', the usual input
> values in PostgreSQL beside '0' and '1'. It's not that the people don't
> use true/false, they use this a lot. But they expect boolean variable
> in PHP working like a bolean column in PG ... without casts, without
> extra workarounds in the code.
>
>
>
>
If your code is prepared to emit t/f but not accept it then that seems
to violate Postel's admonition: "Be *liberal* in what you *accept*, and
*conservative* in what you send."
cheers
andrew
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Dunstan | 2007-12-27 16:58:50 | Re: Unworkable column delimiter characters for COPY |
Previous Message | Tom Lane | 2007-12-27 15:37:07 | Unworkable column delimiter characters for COPY |