Re: BUG #15974: Concact with || doesn't work, but function CONCAT () works - Mailing list pgsql-bugs

From David G. Johnston
Subject Re: BUG #15974: Concact with || doesn't work, but function CONCAT () works
Date
Msg-id CAKFQuwaEtH56SDFBD3-hofpFBNbNDqzG66EC0gPLFbmSbnBLbg@mail.gmail.com
Whole thread Raw
In response to BUG #15974: Concact with || doesn't work, but function CONCAT () works  (PG Bug reporting form <noreply@postgresql.org>)
List 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 by date:

Previous
From: Tom Lane
Date:
Subject: Re: data modifying WITH seems to drop rows in cascading updates -- bug?
Next
From: PG Bug reporting form
Date:
Subject: BUG #15975: Copy from large text files on Windows returns "iso-8859-1 error"