Skip site navigation (1) Skip section navigation (2)

Re: Binary data type with other output method

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 (view raw or flat)
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

In response to

Responses

pgsql-hackers by date

Next:From: Andrew DunstanDate: 2007-12-27 16:58:50
Subject: Re: Unworkable column delimiter characters for COPY
Previous:From: Tom LaneDate: 2007-12-27 15:37:07
Subject: Unworkable column delimiter characters for COPY

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group