From: Marko Tiikkaja <marko@joh.to>
To: Michael Paquier <michael.paquier@gmail.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Daniel Verite <daniel@manitou-mail.org>
Cc: PostgreSQL hackers <pgsql-hackers@postgresql.org>
Subject: Re: psql: add \pset true/false
Date: Thu, 12 Nov 2015 14:06:28 +0100
Message-ID: <56448ED4.5070702@joh.to> (raw)
In-Reply-To: <CAB7nPqQMOOLpZCGsuxUo9wK0nSRybC=hVBCz77Tt2mwtx9oytg@mail.gmail.com>
References: <0949c317-3ec4-4516-a3aa-33a6cfbf5267@mm>
<5631FCAF.9060204@joh.to>
<27336.1446126627@sss.pgh.pa.us>
<CAB7nPqQMOOLpZCGsuxUo9wK0nSRybC=hVBCz77Tt2mwtx9oytg@mail.gmail.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-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
--
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: marko@joh.to, michael.paquier@gmail.com, tgl@sss.pgh.pa.us, daniel@manitou-mail.org
Subject: Re: psql: add \pset true/false
In-Reply-To: <56448ED4.5070702@joh.to>
* 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