Search code examples
arrayspostgresqlsql-likeanyunnest

Find rows where text array contains value similar to input


I'm trying to get rows where a column of type text[] contains a value similar to some user input.

What I've thought and done so far is to use the 'ANY' and 'LIKE' operator like this:

select * from someTable where '%someInput%' LIKE ANY(someColum);

But it doesn't work. The query returns the same values as that this query:

select * from someTable where 'someInput' = ANY(someColum);

I've got good a result using the unnest() function in a subquery but I need to query this in WHERE clause if possible.

Why doesn't the LIKE operator work with the ANY operator and I don't get any errors? I thought that one reason should be that ANY operator is in the right-hand of query, but ...

Is there any solution to this without using unnest() and if it is possible in WHERE clause?


Solution

  • ANY is not an operator but an SQL construct that can only be used to the right of an operator. More:

    The LIKE operator - or more precisely: key word, that is rewritten with to the ~~ operator in Postgres internally - expects the value to the left and the pattern to the right. There is no COMMUTATOR for this operator (like there is for the simple equality operator =) so Postgres cannot flip operands.

    Your attempt:

    select * from someTable where '%someInput%' LIKE ANY(someColum);
    

    ... has left and right operand backwards. '%someInput%' is the value and elements of the array column someColum are taken to be patterns, which is not what you want.

    It would have to be something like ANY (someColum) LIKE '%someInput%' - but the ANY construct is only allowed to the right of an operator. You are hitting a road block.

    Related:

    You can normalize your relational design and save elements of the array in separate rows in a separate table. Barring that, unnest() is the solution, as you already found yourself. But while you are only interested in the existence of at least one matching element, an EXISTS subquery will be most efficient and avoid duplicates in the result. Postgres can stop the search as soon as the first match is found:

    SELECT *
    FROM   tbl
    WHERE  EXISTS (
        SELECT -- SELECT list can be empty for this purpose
        FROM   unnest(someColum) elem
        WHERE  elem LIKE '%someInput%'
      );
    

    You may want to escape special characters in someInput. See:

    Careful with the negation (NOT LIKE ALL (...)) when NULL can be involved: