From: Laurenz Albe <laurenz.albe@cybertec.at>
To: yanliang lei <msdnchina@163.com>
To: pgsql-docs@lists.postgresql.org <pgsql-docs@lists.postgresql.org>
Subject: Re: suggest about bpchar data type in the document
Date: Wed, 14 Sep 2022 18:48:46 +0200
Message-ID: <41fe0ea52f9803649ae876d4d14b2b7ca89ffc06.camel@cybertec.at> (raw)
In-Reply-To: <120b3084.56b6.1833b5ffe4b.Coremail.msdnchina@163.com>
References: <120b3084.56b6.1833b5ffe4b.Coremail.msdnchina@163.com>
On Wed, 2022-09-14 at 17:41 +0800, yanliang lei wrote:
> I hope that：
>
> in the https://www.postgresql.org/docs/14/datatype-characterin.html ，It needs to be written clearly “bpchar” data type，
>
> and in the above url, Only mentioned “blank padded” ，If someone does not know this knowledge point（blank padded =bp），he/she will make a detour in the study of character datatype。
>
> so，To make the document more friendly, I suggest that： in the https://www.postgresql.org/docs/14/datatype-characterin.htm ，It needs to be written clearly “bpchar” data type。
+1
I think that adding "bpchar(n)" in table 8.4 would be a good thing.
Yours,
Laurenz Albe
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-docs@postgresql.org
Cc: laurenz.albe@cybertec.at, msdnchina@163.com, pgsql-docs@lists.postgresql.org
Subject: Re: suggest about bpchar data type in the document
In-Reply-To: <41fe0ea52f9803649ae876d4d14b2b7ca89ffc06.camel@cybertec.at>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox