Regardless, please provide feedback on my queries above then we can consider next steps. 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'. Lastname character varying(256) COLLATE pg_catalog."default",įirstname character varying(256) COLLATE pg_catalog."default", 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:
0 Comments
Leave a Reply. |