I believe that RDBMS-specific options are intended to be used in Freehand SQL statements instead. Middleinitial character varying(40) COLLATE pg_catalog.'default',Īlso, just so I have a deeper understanding of this scenario, are you unable to use ILIKE in a Freehand SQL statement in your use case? If this is true, can you please explain why this is not possible so I can submit this along with the enhancement request? The reason I ask this is because I don't believe any of our 'Configure Filter' options contain RDBMS-specific options by design, as for example, a PostgreSQL-specific option such as ILIKE being available would likely be confusing a majority of our users', considering it wouldn't work for other more common RDBMS'. ILIKE There are no ILIKE condition in Oracle SQL, but you still can have alternative way to do it. Lastname character varying(256) COLLATE pg_catalog.'default',įirstname character varying(256) COLLATE pg_catalog.'default', Because of the way SQL handles NULL, there are some special operations available.

in POSIX regular expressions) matches zero or more characters in the input (similar to. Have you already confirmed using 'Contains' doesn't work in your use case? From my understanding PostgreSQL is case-insensitive by default, and looking at how the tables are created by yellowfin installer, it looks like it does it in a case insensitive way: Create a BooleanExpression case insensitive (if the database supports it) pattern match of the receiver with the given patterns. The pattern is a string which is matched literally and case-insensitively, with exception for the following special symbols: matches any one character in the input (similar to.

Ilike in sql