| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Greg Stark <stark(at)mit(dot)edu> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, 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:42:56 |
| Message-ID: | 20151028234256.GM29811@alap3.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2015-10-28 23:38:45 +0000, Greg Stark wrote:
> 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 data type neutral, and there's no representation of NULL that's
definitely discernible from the corresponding string. So I don't see
those being the same.
This seems like opening a can of worms to me. Why not add formatting
options in psql for other data types?
- Andres
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Haribabu Kommi | 2015-10-29 00:13:00 | Re: BUG #13741: vacuumdb does not accept valid password |
| Previous Message | Greg Stark | 2015-10-28 23:38:45 | Re: psql: add \pset true/false |