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
From f5cb97a9ff7f7d0df5f8fe8a8403b5298465784e Mon Sep 17 00:00:00 2001
From: Laurenz Albe <laurenz.a...@cybertec.at>
Date: Wed, 28 Sep 2022 08:14:11 +0200
Subject: [PATCH] Document "bpchar" as character data type

"bpchar" is our internal name for "character", but it should
be documented as an alternative name to avoid confusion.

Per request from Yanliang Lei.

Discussion: https://postgr.es/m/120b3084.56b6.1833b5ffe4b.coremail.msdnch...@163.com
---
 doc/src/sgml/datatype.sgml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/doc/src/sgml/datatype.sgml b/doc/src/sgml/datatype.sgml
index 0258b192e0..b844e379b9 100644
--- a/doc/src/sgml/datatype.sgml
+++ b/doc/src/sgml/datatype.sgml
@@ -1169,7 +1169,7 @@ SELECT '52093.89'::money::numeric::float8;
         <entry>variable-length with limit</entry>
        </row>
        <row>
-        <entry><type>character(<replaceable>n</replaceable>)</type>, <type>char(<replaceable>n</replaceable>)</type></entry>
+        <entry><type>character(<replaceable>n</replaceable>)</type>, <type>char(<replaceable>n</replaceable>)</type>, <type>bpchar(<replaceable>n</replaceable>)</type></entry>
         <entry>fixed-length, blank padded</entry>
        </row>
        <row>
-- 
2.37.3

Reply via email to