| From: | Jeff Davis <pgsql(at)j-davis(dot)com> |
|---|---|
| To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, Sergei Katkovsky <skatkovsky(at)gmail(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "pgsql-docs(at)lists(dot)postgresql(dot)org" <pgsql-docs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: BPCHAR description in 8.3. Character Types is misleading and incomplete |
| Date: | 2025-10-16 15:21:16 |
| Message-ID: | 6e0741dec0f56692dece5a961533c43f3594d0f0.camel@j-davis.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
On Thu, 2025-10-16 at 08:36 -0400, David G. Johnston wrote:
> A given value has a finite length and there is just no restriction on
> what that length is. All trailing spaces in the input are considered
> padding for purposes of comparison i.e., manually padding is added by
> the user as opposed to the system.
I see -- so it means that the padding came from somewhere else (not the
type).
> I would leave the note of blank-padded for both and just point out
> the automatic vs manual distinction.
Yeah, it's a table, so if a user is confused, they can read the text
below it. I'm fine with that.
If you think the text below should be improved, do you have a wording
suggestion?
Regards,
Jeff Davis
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David G. Johnston | 2025-10-16 18:11:10 | BPCHAR description in 8.3. Character Types is misleading and incomplete |
| Previous Message | Sergei Katkovsky | 2025-10-16 14:19:51 | Re: BPCHAR description in 8.3. Character Types is misleading and incomplete |