It doesn't look like this patch is going anywhere. I agree with Tom's
comments that we need to think how this works for all datatypes, not
just booleans. And a simple substitution of values isn't enough; an
application might want to output all integers in hex, for example. A
custom domain in th
2012/9/2 Tom Lane :
> I wrote:
>> Phil Sorber writes:
>>> What my patch was intended to do was let the end user set boolean
>>> output to any arbitrary values. While foo/bar is pretty useless, it
>>> was meant to reinforce that it was capable of any arbitrary value. I
>>> can think of a decent lis
2012/9/2 Phil Sorber :
> On Sun, Sep 2, 2012 at 1:13 AM, Pavel Stehule wrote:
>> -- Forwarded message --
>> From: Pavel Stehule
>> Date: 2012/9/1
>> Subject: PATCH: psql boolean display
>> To: Phil Sorber
>>
>>
>> Hello
>>
>> I am looking to your patch:
>>
>> I have only one note
I wrote:
> Phil Sorber writes:
>> What my patch was intended to do was let the end user set boolean
>> output to any arbitrary values. While foo/bar is pretty useless, it
>> was meant to reinforce that it was capable of any arbitrary value. I
>> can think of a decent list of other output an end us
Phil Sorber writes:
> What my patch was intended to do was let the end user set boolean
> output to any arbitrary values. While foo/bar is pretty useless, it
> was meant to reinforce that it was capable of any arbitrary value. I
> can think of a decent list of other output an end user might want,
On Sun, Sep 2, 2012 at 1:13 AM, Pavel Stehule wrote:
> -- Forwarded message --
> From: Pavel Stehule
> Date: 2012/9/1
> Subject: PATCH: psql boolean display
> To: Phil Sorber
>
>
> Hello
>
> I am looking to your patch:
>
> I have only one note. I don't think so using any text for
-- Forwarded message --
From: Pavel Stehule
Date: 2012/9/1
Subject: PATCH: psql boolean display
To: Phil Sorber
Hello
I am looking to your patch:
I have only one note. I don't think so using any text for values
"true" and "false" is good idea. I don't see a sense of any specia
