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

Поиск
Список
Период
Сортировка
От David G. Johnston
Тема Re: BUG #17258: Unexpected results in CHAR(1) data type
Дата
Msg-id CAKFQuwbF9=HD+nBxYX4QfMEA68zSNz_OdUqpW-dQDDdotp08kg@mail.gmail.com
обсуждение исходный текст
Ответ на Re: BUG #17258: Unexpected results in CHAR(1) data type  (Mark Dilger <mark.dilger@enterprisedb.com>)
Ответы Re: BUG #17258: Unexpected results in CHAR(1) data type  (Mark Dilger <mark.dilger@enterprisedb.com>)
Список pgsql-bugs
On Fri, Oct 29, 2021 at 3:09 PM Mark Dilger <mark.dilger@enterprisedb.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.

В списке pgsql-bugs по дате отправления:

Предыдущее
От: Mark Dilger
Дата:
Сообщение: Re: BUG #17258: Unexpected results in CHAR(1) data type
Следующее
От: Mark Dilger
Дата:
Сообщение: Re: BUG #17258: Unexpected results in CHAR(1) data type