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 06:11:56 |
Message-ID: | ed0438be-ee6c-7e25-e39d-ae56982dc1de@gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
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%'
> I glanced through our code with grep pipelines and found some hundred
> places which would be affected by this problem. I'm not interested in a
> religious discussion if or if not this behaviour of PG is correcter or
> better than in Sybase. It's just different to Sybase.
SQL Server derives from Sybase, and it would also fail on this statement.
> Any hints to address this problem? Or is there any compile time option
> for the PG server to address this?
>
> Thanks
>
> matthias
--
Angular momentum makes the world go 'round.
From | Date | Subject | |
---|---|---|---|
Next Message | Matthias Apitz | 2019-09-13 06:48:59 | Re: PG SQL and LIKE clause |
Previous Message | Pavel Stehule | 2019-09-13 05:33:10 | Re: PG SQL and LIKE clause |