Re: The result of the pattern matching is incorrect when the pattern string is bpchar type - Mailing list pgsql-bugs

From Andrew Gierth
Subject Re: The result of the pattern matching is incorrect when the pattern string is bpchar type
Date
Msg-id 87k1co4hfu.fsf@news-spur.riddles.org.uk
Whole thread Raw
In response to Re: The result of the pattern matching is incorrect when the patternstring is bpchar type  ("David G. Johnston" <david.g.johnston@gmail.com>)
List pgsql-bugs
>>>>> "David" == David G Johnston <david.g.johnston@gmail.com> writes:

 >> There are two tables with the type of column is char. when Using a
 >> 'like' predicate in a join condition will result in an incorrect
 >> result. Because there is no 'like' operator that left operand and
 >> right operand are all bpchar.(bpchar ~~ bpchar), final the operator
 >> 'bpchar ~~ text' will be found form candidate set. so database do
 >> the cast from bpchar to text, The space at the end of the string was
 >> removed during the cast.

 David> A similar complaint was made the other day; Tom's response
 David> succinctly sums up the prevailing opinion as to the character
 David> type.

It's also listed as WONTFIX here:

https://wiki.postgresql.org/wiki/PostgreSQL_vs_SQL_Standard#Trailing_spaces_in_character.28n.29

though I guess adding the LIKE case as an example there might be good.

-- 
Andrew (irc:RhodiumToad)



pgsql-bugs by date:

Previous
From: "David G. Johnston"
Date:
Subject: Re: BUG #15904: ERROR: argument of LIMIT must not contain variables
Next
From: Tom Lane
Date:
Subject: Re: ERROR: found unexpected null value in index