Re: BPCHAR description in 8.3. Character Types is misleading and incomplete - Mailing list pgsql-docs

From Laurenz Albe
Subject Re: BPCHAR description in 8.3. Character Types is misleading and incomplete
Date
Msg-id 96ad1acfb43cc73b0cdbe74719f035b1ee3f77c0.camel@cybertec.at
Whole thread Raw
In response to Re: BPCHAR description in 8.3. Character Types is misleading and incomplete  (Sergei Katkovsky <skatkovsky@gmail.com>)
Responses Re: BPCHAR description in 8.3. Character Types is misleading and incomplete
List pgsql-docs
On Mon, 2025-10-20 at 16:42 +0400, Sergei Katkovsky wrote:
> On Sat, Oct 18, 2025 at 2:36 AM Laurenz Albe <laurenz.albe@cybertec.at> wrote:
>
> > But perhaps it is really better to leave things as they are now, perhaps
> > replacing "blank-trimming", perhaps as "variable-length string that ignores
> > training blanks".
>
> Looks like nobody is against "insignificant/ignorable trailing
> whitespace" or anything like that anymore? Am I right?

Any verbal description will never completely represent the facts.
But I'd say that "ignores trailing blanks" (not tabs, for example)
is a fairly accurate description.

Yours,
Laurenz Albe



pgsql-docs by date:

Previous
From: Sergei Katkovsky
Date:
Subject: Re: BPCHAR description in 8.3. Character Types is misleading and incomplete
Next
From: "Euler Taveira"
Date:
Subject: Re: Use uppercase keywords in foreign key tutorial