Re: Add \pset options for boolean value display
| От | Pavel Stehule |
|---|---|
| Тема | Re: Add \pset options for boolean value display |
| Дата | |
| Msg-id | CAFj8pRAFFrVB6XcWjHjsrhnuGtt3KdQEdR4vDbtS9vcL7Ytzkw@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: Add \pset options for boolean value display (Álvaro Herrera <alvherre@kurilemu.de>) |
| Список | pgsql-hackers |
út 21. 10. 2025 v 9:38 odesílatel Álvaro Herrera <alvherre@kurilemu.de> napsal:
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’
>
> To keep in line with:
>
> \pset null ‘(null)’
Uhm. I don't know. No technical limitation AFAICS. It looks a bit
weird to me, because those names are so generic; but also I cannot
really object to them. That said, such a last-minute bikeshed comment
seems like a perfect way to kill your patch.
I'll gladly take a vote.
I think so this is little bit different case
In this context I see three "safe" variants like
short: t, f
long: true, false
localized: nepravda, pravda (if this is available)
localized short is probably very messy - like 'n' and 'p' for Czech language and never be used
In the Czech environment we mostly don't translate boolean constants in computer science.
Regards
Pavel
Null is different - there is not known any formal symbol for null.
--
Álvaro Herrera Breisgau, Deutschland — https://www.EnterpriseDB.com/
"On the other flipper, one wrong move and we're Fatal Exceptions"
(T.U.X.: Term Unit X - http://www.thelinuxreview.com/TUX/)
В списке pgsql-hackers по дате отправления: