| From: | Marko Tiikkaja <marko(at)joh(dot)to> |
|---|---|
| To: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | 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-12 13:06:28 |
| Message-ID: | 56448ED4.5070702@joh.to |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 11/12/15 1:50 PM, Michael Paquier wrote:
> FWIW, I am -1 on the concept of enforcing output values for particular
> datatypes because that's not the job of psql
In my view, the job of psql is to make working with a postgres database
easy for us human beings. That means (among other things) formatting
and aligning query output for readability. I don't see how reformatting
unreadable boolean values meant for computers is that big of a stretch.
.m
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2015-11-12 13:15:38 | Re: Multixid hindsight design |
| Previous Message | Kouhei Kaigai | 2015-11-12 12:59:47 | Re: CustomScan support on readfuncs.c |