Re: BUG #17258: Unexpected results in CHAR(1) data type

> On Oct 29, 2021, at 3:09 PM, Mark Dilger <mark(dot)dilger(at)enterprisedb(dot)com> wrote:
>
> most of the functionality involving char(n)

...

> and those functions that do directly take a bpchar type for comparison purposes trigger the "semantically insignificant and disregarded" bit

I meant the "most of the functionality" qualifier to apply to the second part, meaning "most of the functions that do..." but on re-reading, my grammar didn't accomplish that. I now understand why David Johnston corrected me here:

> On Oct 29, 2021, at 3:13 PM, David G. Johnston <david(dot)g(dot)johnston(at)gmail(dot)com> wrote:
>
> As I noted in a prior reply, octet_length(char) does the length computation with the padding spaces. So it is possible for char input functions to do the expected thing.

You are correct, sir.

—
Mark Dilger
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company