Re: BUG #15974: Concact with || doesn't work, but function CONCAT () works

Поиск
Список
Период
Сортировка
От David G. Johnston
Тема Re: BUG #15974: Concact with || doesn't work, but function CONCAT () works
Дата
Msg-id CAKFQuwaEtH56SDFBD3-hofpFBNbNDqzG66EC0gPLFbmSbnBLbg@mail.gmail.com
обсуждение исходный текст
Ответ на BUG #15974: Concact with || doesn't work, but function CONCAT () works  (PG Bug reporting form <noreply@postgresql.org>)
Список pgsql-bugs
Дерево обсуждения
On Fri, Aug 23, 2019 at 4:17 AM PG Bug reporting form <noreply@postgresql.org> wrote:
The following bug has been logged on the website:

Bug reference:      15974
Logged by:          Tessari Andrea
Email address:      tessari@gmail.com
PostgreSQL version: 11.4
Operating system:   linux - Red Hat 7.6
Description:       

Example.
 ( I test on postgres 11.4 and postgres 10.9 (edb) )

create table AA3 (CLIV CHAR(2), SSTT CHAR(1));
 INSERT INTO AA3 (CLIV,SSTT)  VALUES ('  ','2');

In general most behaviors involving the "char" data type are what they are and you can either accept them as-is or change to text to get more logical/consistent behavior.

If you want a more in depth analysis of how char behaves in various situations there are a number of posts in the archives where people have taken the time to explain in detail what is happening.  Or someone may do that here...but that someone isn't me.

If you want to claim these are buggy you'd need to point to documentation that isn't being adhered to not just expectations.

David J.

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

Предыдущее
От: Tom Lane
Дата:
Сообщение: Re: data modifying WITH seems to drop rows in cascading updates -- bug?
Следующее
От: PG Bug reporting form
Дата:
Сообщение: BUG #15975: Copy from large text files on Windows returns "iso-8859-1 error"