| From: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
|---|---|
| To: | Sergei Katkovsky <skatkovsky(at)gmail(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Jeff Davis <pgsql(at)j-davis(dot)com>, pgsql-docs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BPCHAR description in 8.3. Character Types is misleading and incomplete |
| Date: | 2025-10-20 14:22:50 |
| Message-ID: | 96ad1acfb43cc73b0cdbe74719f035b1ee3f77c0.camel@cybertec.at |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | 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(dot)albe(at)cybertec(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Euler Taveira | 2025-10-21 01:37:20 | Re: Use uppercase keywords in foreign key tutorial |
| Previous Message | Sergei Katkovsky | 2025-10-20 12:42:30 | Re: BPCHAR description in 8.3. Character Types is misleading and incomplete |