Subject: Re: psql: add \pset true/false
To: Jim Nasby <Jim.Nasby@BlueTreble.com>, Tom Lane <tgl@sss.pgh.pa.us>
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>
Cc: Marko Tiikkaja <marko@joh.to>, Daniel Verite <daniel@manitou-mail.org>,
 PostgreSQL hackers <pgsql-hackers@postgresql.org>
From: Peter Eisentraut <peter_e@gmx.net>
Message-ID: <5649334C.50902@gmx.net>
Date: Sun, 15 Nov 2015 20:37:16 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:38.0)
 Gecko/20100101 Thunderbird/38.3.0
MIME-Version: 1.0
In-Reply-To: <5648E8F3.7070202@BlueTreble.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
Precedence: bulk
Sender: pgsql-hackers-owner@postgresql.org

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.


-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers