Content-Type: text/plain; charset="iso-8859-15"
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: psql: add \pset true/false
From: "Daniel Verite" <daniel@manitou-mail.org>
To: "Marko Tiikkaja" <marko@joh.to>
CC: "PostgreSQL hackers" <pgsql-hackers@postgresql.org>
In-Reply-To: <56308F56.8060908@joh.to>
Date: Thu, 29 Oct 2015 11:51:04 +0100
Message-ID: <0949c317-3ec4-4516-a3aa-33a6cfbf5267@mm>
Precedence: bulk
Sender: pgsql-hackers-owner@postgresql.org

	Marko Tiikkaja wrote:

> Since the default t/f output for booleans is not very user friendly,=20
> attached is a patch which enables you to do for example the following:

Personally I think it would be worth having, but how about
booleans inside ROW() or composite types ?

test=3D> \pset true 1
Boolean TRUE display is "1".
test=3D> \pset false 0
Boolean FALSE display is "0".

test #1:=20

test=3D> select 't'::bool,'f'::bool;
 bool | bool=20
------+------
 1    | 0

test #2:

test=3D> select ('t'::bool,'f'::bool);
  row=20=20
-------
 (t,f)

test #3:

test=3D> create type abc as (a bool, b bool, c bool);
test=3D> select (true,false,true)::abc;
   row=09=20
---------
 (t,f,t)


I understand that the patch translates t/f only if the output type
has the OID for bool, which is not the case in #2 or #3, but I guess
users would expect #2 to output (1,0) and #3 (1,0,1).


Best regards,
--=20
Daniel V=E9rit=E9
PostgreSQL-powered mailer: http://www.manitou-mail.org
Twitter: @DanielVerite


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