On 11/12/15 3:09 PM, Tom Lane wrote:
Peter Eisentraut <pete...@gmx.net> writes:
Plus we already have \pset numericlocale as a similar feature in psql.
But \pset numericlocale is also a crock. It doesn't affect COPY output
for instance, and its ability to identify which data types it should apply
to is really shaky. And it's virtually unused, as demonstrated by the
fact that serious bugs in it went undetected for many years (cf 4778a0bda,
77130fc14). That's a really poor advertisement for the usefulness of the
proposed feature.
My $0.02 is that something that's type-specific belongs with the type,
not with clients.
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.
--
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
