| From: | Greg Stark <stark(at)mit(dot)edu> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Marko Tiikkaja <marko(at)joh(dot)to>, PostgreSQL hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: psql: add \pset true/false |
| Date: | 2015-10-28 23:38:45 |
| Message-ID: | CAM-w4HOxmbfjNFBwBAd2=eZnqgJO5EHpZ9857eyMPRE5uhD-RQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Oct 28, 2015 at 10:52 PM, Robert Haas <robertmhaas(at)gmail(dot)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 not like 'f'
and 't' are terribly common and probably different from how they
render in whatever driver the user's probably coding to.
On the other hand if their driver isn't mapping booleans to a native
data type and just providing the Postgres text output then then this
is only risking more confusion by presenting the user with a rendering
that's different from what they need to be expecting. IIRC this is the
case for the PHP driver for example.
--
greg
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2015-10-28 23:42:56 | Re: psql: add \pset true/false |
| Previous Message | Robert Haas | 2015-10-28 22:52:15 | Re: psql: add \pset true/false |