From: Jim Nasby <Jim.Nasby@BlueTreble.com>
To: Peter Eisentraut <peter_e@gmx.net>
To: 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: Wed, 2 Dec 2015 12:10:18 -0600
Message-ID: <565F340A.8010705@BlueTreble.com> (raw)
In-Reply-To: <5649334C.50902@gmx.net>
References: <0949c317-3ec4-4516-a3aa-33a6cfbf5267@mm>
<5631FCAF.9060204@joh.to>
<27336.1446126627@sss.pgh.pa.us>
<5644FCE0.2030405@gmx.net>
<20643.1447362580@sss.pgh.pa.us>
<5648E8F3.7070202@BlueTreble.com>
<5649334C.50902@gmx.net>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-hackers>
On 11/15/15 7:37 PM, Peter Eisentraut wrote:
> On 11/15/15 3:20 PM, Jim Nasby wrote:
>> As to the argument about displaying a check or an X, why should that
>> capability only exist for boolean types? For example, why not allow psql
>> to convert a numeric value into a bar of varying sizes? I've frequently
>> emulated that with something like SELECT repeat( '*', blah * 30 /
>> max_of_blah ). I'm sure there's other examples people could think of.
>
> Well, why not? The question there is only how many marginal features
> you want to stuff into psql, not whether it's the right place to stuff them.
I was more thinking it would be nice to be able to temporarily
over-ride/wrap what an output function is doing. AFAIK that would allow
this to work everywhere (row(), copy, etc). I don't know of any remotely
practical way to do that, though.
--
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Experts in Analytics, Data Architecture and PostgreSQL
Data in Trouble? Get it in Treble! http://BlueTreble.com
--
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: Jim.Nasby@BlueTreble.com, peter_e@gmx.net, tgl@sss.pgh.pa.us, marko@joh.to, daniel@manitou-mail.org
Subject: Re: psql: add \pset true/false
In-Reply-To: <565F340A.8010705@BlueTreble.com>
* 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