| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Álvaro Herrera <alvherre(at)kurilemu(dot)de> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Add \pset options for boolean value display |
| Date: | 2025-11-03 17:16:30 |
| Message-ID: | CAKFQuwbNhHz-wcJbFSw19n1n6a-t4PTmFdMM0Yr=MxHchP4Opg@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Monday, November 3, 2025, Álvaro Herrera <alvherre(at)kurilemu(dot)de> wrote:
> On 2025-Oct-21, Álvaro Herrera wrote:
> > On 2025-Oct-20, David G. Johnston wrote:
> > > Thank you. Seems good from a quick read. I’m regretting the choice
> of the
> > > display_ prefix; is there any technical limitation or other opposition
> to
> > > using just true and false?
> > >
> > > \pset true ‘true’
> > > \pset false ‘false’
>
> > Uhm. I don't know. [...] I'll gladly take a vote.
>
> I got zero votes and lots of digression, so I have pushed with your
> original choice of "display_true" and "display_false". The "true" and
> "false" variable names sound too generic and I think they're more likely
> to cause confusion. I think "null" is not a great name either, but it's
> been there since forever so I'm not going to propose changing it.
Thank you.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Álvaro Herrera | 2025-11-03 17:44:31 | psql --help=variables missing csv_fieldsep |
| Previous Message | Jelte Fennema-Nio | 2025-11-03 17:04:28 | Re: Bump soft open file limit (RLIMIT_NOFILE) to hard limit on startup |