"Haszlakiewicz, Eric" <EHASZLA@transunion.com> writes:
>> Cast the char(n) column to text or varchar, and it should work more
>> like you're expecting.
> Yeah, I figured that much. I was hoping for a connection-wide or
> database-wide setting, so I wouldn't have to go change all my SQL
> statements.
Well, you could experiment with removing the char(n) variant of the ~~
operator, but if it breaks you get to keep both pieces.
regards, tom lane