| From: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
|---|---|
| To: | yanliang lei <msdnchina(at)163(dot)com>, "pgsql-docs(at)lists(dot)postgresql(dot)org" <pgsql-docs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: suggest about bpchar data type in the document |
| Date: | 2022-09-14 16:48:46 |
| Message-ID: | 41fe0ea52f9803649ae876d4d14b2b7ca89ffc06.camel@cybertec.at |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Chandler Gonzales | 2022-09-16 18:57:25 | Clarifying docs on nuance of select and update policies |
| Previous Message | yanliang lei | 2022-09-14 09:41:30 | suggest about bpchar data type in the document |