From: | "Daniel Verite" <daniel(at)manitou-mail(dot)org> |
---|---|
To: | "Marko Tiikkaja" <marko(at)joh(dot)to> |
Cc: | "PostgreSQL hackers" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: psql: add \pset true/false |
Date: | 2015-10-29 10:51:04 |
Message-ID: | 0949c317-3ec4-4516-a3aa-33a6cfbf5267@mm |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Marko Tiikkaja wrote:
> Since the default t/f output for booleans is not very user friendly,
> 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=> \pset true 1
Boolean TRUE display is "1".
test=> \pset false 0
Boolean FALSE display is "0".
test #1:
test=> select 't'::bool,'f'::bool;
bool | bool
------+------
1 | 0
test #2:
test=> select ('t'::bool,'f'::bool);
row
-------
(t,f)
test #3:
test=> create type abc as (a bool, b bool, c bool);
test=> select (true,false,true)::abc;
row
---------
(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,
--
Daniel Vérité
PostgreSQL-powered mailer: http://www.manitou-mail.org
Twitter: @DanielVerite
From | Date | Subject | |
---|---|---|---|
Next Message | Marko Tiikkaja | 2015-10-29 11:02:07 | Re: psql: add \pset true/false |
Previous Message | Vladimir Borodin | 2015-10-29 10:33:18 | Re: [ADMIN] Replication slots and isolation levels |