Is there any substitute for Postgres ALL Operator?

Asked Mar 29 '21 at 18:14

Active Mar 30 '21 at 00:56

Viewed 116 times

I'm trying to execute this:

SELECT id, title FROM book 
    WHERE author_id != all('{
        {d778ee4f-e7cf-436e-8975-8f6ca2cccb2a},
        {17db25c6-0d61-4f23-826e-4f2982bcc490}
    }'::uuid[]);

This select SQL works perfectly in Postgres but, the main problem is because I'm using JsqlParser to parse this statement, at this moment != all an error is thrown. How can I change just this code snippet here ! = All and get the same result?

Edit1: I tried not in:

SELECT id, title from book 
    WHERE author_id NOT IN ('{
        {d778ee4f-e7cf-436e-8975-8f6ca2cccb2a},
        {17db25c6-0d61-4f23-826e-4f2982bcc490}
    }'::uuid[]);

SQL Error [42883]: ERROR: operator does not exist: uuid <> uuid[]

Edit2: I tried <> to

SELECT id, title from book 
    WHERE author_id <> ('{
        {d778ee4f-e7cf-436e-8975-8f6ca2cccb2a},
        {17db25c6-0d61-4f23-826e-4f2982bcc490}
    }'::uuid[]);

SQL Error [42883]: ERROR: operator does not exist: uuid <> uuid[]

Obs. I already opened an issue here: JsqlParser repository

edited Mar 30 '21 at 00:56

asked Mar 29 '21 at 18:14

rcorrent

2

Have you tried using `not in` ? – Dario Petrillo Mar 29 '21 at 18:15
1

Did you try the standard not equals operator `<>` – Mar 29 '21 at 18:15
If the problem is with JsqlParser, you should tag it. – jjanes Mar 29 '21 at 20:37
if the filter inside where is just going to be two values why not just go with AND ? – vishal N Mar 30 '21 at 03:34
must you use arrays? I suspect it is the use of arrays that is leading to the issue as indicated by `uuid <> uuid[]` only one side of that refers to an array – Paul Maxwell Mar 30 '21 at 04:15
There are no limits in arrays, I used two as an example. – rcorrent Mar 30 '21 at 16:15

Is there any substitute for Postgres ALL Operator?

0 Answers0