Before you kick me out of the group, can you please explain.
I thought the orig issue was that purposefully spaces/whitespace are being ignored (or not ignored.) in the select. Maybe there was an email in the middle that I missed.
create table matt_test (c1 int)
insert into matt_test values ('123')
insert into matt_test values (' 123')
insert into matt_test values ('123 ')
select c1 from matt_test where c1 = '123'
-- all 3 rows returned.
Is it expected behavior that all 3 rows would be returned (because the space isn’t an INT?)
Works as I would expect with TEXT
create table matt_test2 (c2 text)
insert into matt_test2 values ('123')
insert into matt_test2 values (' 123')
insert into matt_test2 values ('123 ')
select c2 from matt_test2 where c2 = '123'
-- 1 rows returned.
From: mahesh <mahesha_dba@yahoo.com>
Sent: Thursday, June 15, 2023 7:12 AM
To: Scott Ribe <scott_ribe@elevated-dev.com>; Mohammed Aslam <hmdaslam97@gmail.com>; pgsql-admin@lists.postgresql.org
Cc: Wetmore, Matthew (CTR) <Matthew.Wetmore@express-scripts.com>; Tom Lane <tgl@sss.pgh.pa.us>; M Sarwar <sarwarmd02@outlook.com>
Subject: [EXTERNAL] Re: The same result for with SPACE and without SPACE
Kindly remove from from the group..
> On Jun 15, 2023, at 7:08 AM, Wetmore, Matthew (CTR) <Matthew.Wetmore@express-scripts.com> wrote:
>
> I can reproduce this with a INT
?
When casting string to integer, trailing spaces do not cause an exception. When casting integer to char(n), the string will be blank padded.