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-28 06:15:57 |
Message-ID: | ccdfa054d8c26b94cf522ef7ceec0112c8f523a2.camel@cybertec.at |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs |
On Wed, 2022-09-14 at 18:48 +0200, Laurenz Albe wrote:
> 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.
Here is a patch for that.
Yours,
Laurenz Albe
Attachment | Content-Type | Size |
---|---|---|
0001-Document-bpchar-as-character-data-type.patch | text/x-patch | 1.2 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2022-09-28 14:48:03 | Re: suggest about bpchar data type in the document |
Previous Message | Elena Indrupskaya | 2022-09-27 12:58:10 | Minor documentation fixes |