[kexi] [Bug 348017] New: kexi unable to accept a 'case insensitive' SQL query using the keyword 'ILIKE'

[Ian Balchin]

https://bugs.kde.org/show_bug.cgi?id=348017

            Bug ID: 348017
           Summary: kexi unable to accept a 'case insensitive' SQL query
                    using the keyword 'ILIKE'
           Product: kexi
           Version: 2.9.3
          Platform: Mint (Ubuntu based)
                OS: Linux
            Status: UNCONFIRMED
          Severity: wishlist
          Priority: NOR
         Component: Queries
          Assignee: kexi-bugs at kde.org
          Reporter: inksi at fables.co.za
                CC: adam at piggz.co.uk, inksi at fables.co.za

When writing an SQL query in the SQL mode, a query using the keyword 'ILIKE' is
declared invalid.

The word 'ILIKE' is not bolded, unlike the word 'LIKE' which is bolded, nor
does Kexi accept this as a valid query

This is using, in my case, Postgresql 8.4



Reproducible: Always

Steps to Reproduce:
1. open a new query in a database
2. construct a query on a table to use the term 'LIKE' (instead of the usual
'=')
3. run the query or click the 'Check Query' button to validate it
4. change the term 'LIKE' to 'ILIKE'
5. run the query or click the 'Check Query' button to validate it

Actual Results:  
In the case of the query containing 'ILIKE', then '5' above produces the
following output

EITHER
The query does not run, returning the Warning box advising "The query you
entered is incorrect"
OR, respectively,
The 'Check Query' button returns "The query is incorrect, syntax error"

Expected Results:  
The query would perform, satisfactorily, returning results based upon a
case-insensitive search.

The postgresql operators ~~, *, !, are not accepted either.

I have not yet tried the noted kludge:
SELECT id FROM groups WHERE LOWER(name)=LOWER('Administrator')

ILIKE would be preferred as a solution, being minimally editable from
established queries.

Operator data error means that a case-insensitive search is a desired solution
in tracking down certain records.

I cannot vouch for what happens using the visual query approach in the 'Design'
mode since I never use this.

-- 
You are receiving this mail because:
You are the assignee for the bug.