From: | Ron <ronljohnsonjr(at)gmail(dot)com> |
---|---|
To: | pgsql-general(at)lists(dot)postgresql(dot)org |
Subject: | Re: PG SQL and LIKE clause |
Date: | 2019-09-13 14:35:06 |
Message-ID: | 1f77ce73-c0f0-d994-6f38-dca9e4c4a47f@gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 9/13/19 9:14 AM, Adrian Klaver wrote:
> On 9/12/19 11:11 PM, Ron wrote:
>> On 9/13/19 12:28 AM, Matthias Apitz wrote:
>>> Hello,
>>>
>>> We're porting a huge Library Management System, written using all kind
>>> of languages one can think of (C, C++, ESQL/C, Perl, Java, ...) on Linux
>>> from the DBS Sybase to PG, millions of lines of code, which works also
>>> with DBS Oracle and in the past with INFORMIX-SE and -ONLINE.
>>>
>>> We got to know that in CHAR columns with trailing blanks a
>>>
>>> SELECT ... FROM ... WHERE name LIKE 'Ali'
>>>
>>> does not match in 'name' having 'Ali '.
>>
>> Did you forget the "%"? Because the SQL standard which PostgreSQL
>> follows is:
>>
>> SELECT ... FROM ... WHERE name LIKE 'Ali%'
>
> The above is if you want to find a string starting with 'Ali'. If you are
> looking for the complete string 'Ali' then it is appropriate. The OP is
> looking for a way to automatically match a complete string against a right
> stripped string from a CHAR field.
This is highly dependent on implementation. On the RDBMS that I used to
work on, trailing whitespace was automatically stripped from CHAR(xx) fields.
--
Angular momentum makes the world go 'round.
From | Date | Subject | |
---|---|---|---|
Next Message | Hans Schou | 2019-09-13 14:39:06 | Re: backing up the data from a single table? |
Previous Message | Ron | 2019-09-13 14:27:58 | Re: backing up the data from a single table? |