Re: PATCH: psql boolean display

From: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
To: "Gurjeet Singh" <singh(dot)gurjeet(at)gmail(dot)com>, "Thom Brown" <thom(at)linux(dot)com>
Cc: "Pavel Stehule" <pavel(dot)stehule(at)gmail(dot)com>, "Robert Haas" <robertmhaas(at)gmail(dot)com>, "Phil Sorber" <phil(at)omniti(dot)com>, "PostgreSQL-development Hackers" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: PATCH: psql boolean display
Date: 2012-08-20 22:28:04
Message-ID: 503273A40200002500049954@gw.wicourts.gov
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Gurjeet Singh <singh(dot)gurjeet(at)gmail(dot)com> wrote:

> On occasions I have wanted psql to emit the full 'True'/'False'
> words instead of cryptic one-letter t/f, which can get lost on
> long rows that get wrapped around on screen. Writing long-winded
> CASE expressions to get the effect is too much for small ad-hoc
> queries.
>
> I thought of inventing a data type whose out-function would emit
> these strings, and tack a ::mybool to the expression I want
> modified. But that would break the applications if somebody pasted
> the same query in an application (JDBC or some such that
> understands boolean) and expected a boolean data type instead of a
> text output of an expression.

The type itself does output true/false; it's just psql that uses
t/f.

test=# select 'true'::boolean::text;
text
------
true
(1 row)

test=# select 'false'::boolean::text;
text
-------
false
(1 row)

That has always seemed quite odd (and occasionally inconvenient) to
me.

-Kevin

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Thom Brown 2012-08-20 22:30:35 Re: PATCH: psql boolean display
Previous Message Phil Sorber 2012-08-20 22:16:37 Re: PATCH: psql boolean display