David G. Johnston wrote:
> > It's \pset null for boolean values
> >
>
> v1, Ready aside from bike-shedding the name.
An annoying weakness of this approach is that it cannot detect
booleans inside arrays or composite types or COPY output,
meaning that the translation of t/f is incomplete.
On Wed, Jun 25, 2025 at 11:03 AM Daniel Verite
wrote:
> David G. Johnston wrote:
>
> > > It's \pset null for boolean values
> > >
> >
> > v1, Ready aside from bike-shedding the name.
>
> An annoying weakness of this approach is that it cannot detect
> booleans inside arrays or composite t
On Tue, Jun 24, 2025 at 3:30 PM Tom Lane wrote:
> "David G. Johnston" writes:
> > On Thu, Mar 20, 2025 at 8:24 PM David G. Johnston <
> > david.g.johns...@gmail.com> wrote:
> >> It's \pset null for boolean values
>
> > v1, Ready aside from bike-shedding the name.
>
> Do we really want this? It'
"David G. Johnston" writes:
> On Thu, Mar 20, 2025 at 8:24 PM David G. Johnston <
> david.g.johns...@gmail.com> wrote:
>> It's \pset null for boolean values
> v1, Ready aside from bike-shedding the name.
Do we really want this? It's the sort of thing that has a strong
potential to break anythin
on"
Date: Wed, 18 Jun 2025 12:20:43 -0700
Subject: [PATCH] Add \pset options for boolean value display
The server's space-expedient choice to use 't' and 'f' to represent
boolean true and false respectively is technically understandable
but visually atrocious. Teac
mat related stuff.
\pset { print_true | print_false } value
David J.
From 4d306939c008ecf7e8ae0036a46218b059a069c7 Mon Sep 17 00:00:00 2001
From: "David G. Johnston"
Date: Thu, 20 Mar 2025 20:03:01 -0700
Subject: [PATCH] Add \pset options for boolean value display
The server's sp
