Re: BPCHAR description in 8.3. Character Types is misleading and incomplete
| От | Jeff Davis |
|---|---|
| Тема | Re: BPCHAR description in 8.3. Character Types is misleading and incomplete |
| Дата | |
| Msg-id | 6e0741dec0f56692dece5a961533c43f3594d0f0.camel@j-davis.com обсуждение исходный текст |
| Ответ на | Re: BPCHAR description in 8.3. Character Types is misleading and incomplete ("David G. Johnston" <david.g.johnston@gmail.com>) |
| Ответы |
Re: BPCHAR description in 8.3. Character Types is misleading and incomplete
|
| Список | 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
В списке pgsql-docs по дате отправления: