Date: Thu, 29 Oct 2015 00:42:56 +0100
From: Andres Freund <andres@anarazel.de>
To: Greg Stark <stark@mit.edu>
Cc: Robert Haas <robertmhaas@gmail.com>, Marko Tiikkaja <marko@joh.to>,
 PostgreSQL hackers <pgsql-hackers@postgresql.org>
Subject: Re: psql: add \pset true/false
Message-ID: <20151028234256.GM29811@alap3.anarazel.de>
References: <56308F56.8060908@joh.to>
 <CA+TgmoYNhwfj1uaAaV58ewTiMHFpzD95VEq=0=TitdKiN_7xJA@mail.gmail.com>
 <CAM-w4HOxmbfjNFBwBAd2=eZnqgJO5EHpZ9857eyMPRE5uhD-RQ@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: 
 <CAM-w4HOxmbfjNFBwBAd2=eZnqgJO5EHpZ9857eyMPRE5uhD-RQ@mail.gmail.com>
Precedence: bulk
Sender: pgsql-hackers-owner@postgresql.org

On 2015-10-28 23:38:45 +0000, Greg Stark wrote:
> On Wed, Oct 28, 2015 at 10:52 PM, Robert Haas <robertmhaas@gmail.com> wrote:
> > 3. I really don't want to end up with a bunch of features of this type
> > for a variety of different data types.
> 
> We already have \pset null which feels very similar.

It's data type neutral, and there's no representation of NULL that's
definitely discernible from the corresponding string. So I don't see
those being the same.


This seems like opening a can of worms to me. Why not add formatting
options in psql for other data types?

- Andres


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