| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Marko Tiikkaja <marko(at)joh(dot)to>, Daniel Verite <daniel(at)manitou-mail(dot)org>, PostgreSQL hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: psql: add \pset true/false |
| Date: | 2015-11-16 01:37:16 |
| Message-ID: | 5649334C.50902@gmx.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Geoghegan | 2015-11-16 01:43:20 | Re: psql: add \pset true/false |
| Previous Message | Peter Eisentraut | 2015-11-16 01:34:43 | Re: psql: add \pset true/false |