Fwd: PATCH: psql boolean display

From: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
To: PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Fwd: PATCH: psql boolean display
Date: 2012-09-02 05:13:19
Message-ID: CAFj8pRBvgKCuVXwXg=ry=hSQ7Q7KgWMQ-foV1A1V2zycv2eozQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

---------- Forwarded message ----------
From: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
Date: 2012/9/1
Subject: PATCH: psql boolean display
To: Phil Sorber <phil(at)omniti(dot)com>

Hello

I am looking to your patch:

I have only one note. I don't think so using any text for values
"true" and "false" is good idea. I don't see a sense of any special
texts like "foo", "bar" from your example.

More strict design is better - I wrote simple modification - it is
based on psql psets - and it add new configuration settings "boolstyle
[char|word]". A advantage of this design is consistency and possible
autocomplete support.

Regards

Pavel

postgres=> select true, false;
bool │ bool
──────┼──────
t │ f
(1 row)

postgres=> \pset boolstyle word
Bool output style is word.
postgres=> select true, false;
bool │ bool
──────┼───────
true │ false
(1 row)

Attachment Content-Type Size
boolstyle.diff application/octet-stream 10.0 KB

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Sergey Koposov 2012-09-02 05:21:13 bitmap scan much slower than index scan, hash_search_with_hash_value
Previous Message Robert Haas 2012-09-02 05:06:28 Re: Yet another failure mode in pg_upgrade