From: Vik Fearing <vik@2ndquadrant.fr>
To: Matthijs van der Vleuten <matthijs@zr40.nl>
To: Brendan Jurd <direvus@gmail.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Marko Tiikkaja <marko@joh.to>
Cc: Daniel Verite <daniel@manitou-mail.org>
Cc: PostgreSQL hackers <pgsql-hackers@postgresql.org>
Subject: Re: psql: add \pset true/false
Date: Thu, 12 Nov 2015 17:51:28 +0100
Message-ID: <5644C390.6040804@2ndquadrant.fr> (raw)
In-Reply-To: <FA73A3C2-9FE4-4122-8D3D-E86C1734F435@zr40.nl>
References: <0949c317-3ec4-4516-a3aa-33a6cfbf5267@mm>
<5631FCAF.9060204@joh.to>
<27336.1446126627@sss.pgh.pa.us>
<CADxJZo1FDyEqwFcF21crkxKbvCkkmHHiRjbJiGphTB=7tGnQpQ@mail.gmail.com>
<FA73A3C2-9FE4-4122-8D3D-E86C1734F435@zr40.nl>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-hackers>
On 11/12/2015 05:41 PM, Matthijs van der Vleuten wrote:
>
>> On 12 Nov 2015, at 14:21, Brendan Jurd <direvus@gmail.com> wrote:
>>
>> On Fri, 30 Oct 2015 at 00:51 Tom Lane <tgl@sss.pgh.pa.us <mailto:tgl@sss.pgh.pa.us>> wrote:
>> The really key argument that hasn't been addressed here is why does such
>> a behavior belong in psql, rather than elsewhere? Surely legibility
>> problems aren't unique to psql users. Moreover, there are exactly
>> parallel facilities for other datatypes on the server side: think
>> DateStyle or bytea_output. So if you were trying to follow precedent
>> rather than invent a kluge, you'd have submitted a patch to create a GUC
>> that changes the output of boolout().
>>
>> I find Tom's analogy to datestyle and bytea_output convincing.
>>
>> +1 for a GUC that changes the behaviour of boolout.
>
> -1 for changing boolout(). It will break anything that receives boolean values from the server. How a client is going to display values (of any type) is logic that should belong in the client, not in the protocol.
I fully agree. This is something I feel should happen in the client.
--
Vik Fearing +33 6 46 75 15 36
http://2ndQuadrant.fr PostgreSQL : Expertise, Formation et Support
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: vik@2ndquadrant.fr, matthijs@zr40.nl, direvus@gmail.com, tgl@sss.pgh.pa.us, marko@joh.to, daniel@manitou-mail.org
Subject: Re: psql: add \pset true/false
In-Reply-To: <5644C390.6040804@2ndquadrant.fr>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox