Add anynonarrayliketext function in PostgreSQL to fix numeric value suggestion error

Author: raviks789

schema/pgsql/schema.sql

@@ -2,6 +2,20 @@ CREATE TYPE boolenum AS ENUM ( 'n', 'y' );
 CREATE TYPE incident_history_event_type AS ENUM ( 'source_severity_changed', 'incident_severity_changed', 'recipient_role_changed', 'escalation_triggered', 'rule_matched', 'opened', 'closed', 'notified' );
 CREATE TYPE frequency_type AS ENUM ( 'MINUTELY', 'HOURLY', 'DAILY', 'WEEKLY', 'MONTHLY', 'QUARTERLY', 'YEARLY' );
 
+-- IPL ORM renders SQL queries with LIKE operators for all suggestions in the search bar,
+-- which fails for numeric and enum types on PostgreSQL. Just like in Icinga DB Web.
+CREATE OR REPLACE FUNCTION anynonarrayliketext(anynonarray, text)
+    RETURNS bool
+    LANGUAGE plpgsql
+    IMMUTABLE
+    PARALLEL SAFE
+    AS $$
+        BEGIN
+            RETURN $1::TEXT LIKE $2;
+        END;
+    $$;
+CREATE OPERATOR ~~ (LEFTARG=anynonarray, RIGHTARG=text, PROCEDURE=anynonarrayliketext);
+
 CREATE TABLE contact (
     id bigserial,
     full_name text NOT NULL,

schema/pgsql/upgrades/013.sql

@@ -0,0 +1,13 @@
+-- IPL ORM renders SQL queries with LIKE operators for all suggestions in the search bar,
+-- which fails for numeric and enum types on PostgreSQL. Just like in Icinga DB Web.
+CREATE OR REPLACE FUNCTION anynonarrayliketext(anynonarray, text)
+    RETURNS bool
+    LANGUAGE plpgsql
+    IMMUTABLE
+    PARALLEL SAFE
+    AS $$
+        BEGIN
+            RETURN $1::TEXT LIKE $2;
+        END;
+    $$;
+CREATE OPERATOR ~~ (LEFTARG=anynonarray, RIGHTARG=text, PROCEDURE=anynonarrayliketext);