From: Tom Lane <tgl@sss.pgh.pa.us>
To: baurzhansahariev@gmail.com
cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #18218: NOT LIKE ANY returns same result as LIKE ANY when
 array items are wrapped into E''
In-reply-to: <18218-8cbdd922e41ea291@postgresql.org>
References: <18218-8cbdd922e41ea291@postgresql.org>
Comments: In-reply-to PG Bug reporting form <noreply@postgresql.org>
	message dated "Thu, 30 Nov 2023 10:54:36 +0000"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <461814.1701349582.1@sss.pgh.pa.us>
Date: Thu, 30 Nov 2023 08:06:22 -0500
Message-ID: <461815.1701349582@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/461815.1701349582%40sss.pgh.pa.us>
Precedence: bulk

PG Bug reporting form <noreply@postgresql.org> writes:
> select 'TextToMatch' like any (array[E'Te\%tch', E'nomatch']); -- true,
> correct
> select 'TextToMatch' NOT like any (array[E'Te\%tch', E'nomatch']); -- true
> but must be false because it's a negated version of the expression above

No, it is not.  "NOT LIKE" is the operator to apply in this context,
so the second expression returns true if the test string is NOT LIKE
either of the array elements.  You could write

NOT ('TextToMatch' like any (array[E'Te\%tch', E'nomatch']))

to get the behavior you are after.  Or write NOT LIKE ALL,
as Orlov suggests.

			regards, tom lane