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

From: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
To: Mark Dilger <mark(dot)dilger(at)enterprisedb(dot)com>
Cc: "<David(at)calascibetta(dot)com>" <David(at)calascibetta(dot)com>, PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Subject: Re: BUG #17258: Unexpected results in CHAR(1) data type
Date: 2021-10-29 22:13:08
Message-ID: CAKFQuwbF9=HD+nBxYX4QfMEA68zSNz_OdUqpW-dQDDdotp08kg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Fri, Oct 29, 2021 at 3:09 PM Mark Dilger <mark(dot)dilger(at)enterprisedb(dot)com>
wrote:

> and those functions that do directly take a bpchar type for comparison
> purposes trigger the "semantically insignificant and disregarded" bit. For
> practical purposes you will frequently hit the one bit or the other.
>
>
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.

David J.

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Mark Dilger 2021-10-29 22:18:30 Re: BUG #17258: Unexpected results in CHAR(1) data type
Previous Message Mark Dilger 2021-10-29 22:09:46 Re: BUG #17258: Unexpected results in CHAR(1) data type