[kexi] [Bug 348017] Add support for 'case insensitive' operator ILIKE for SQL queries

[Ian Balchin]

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

--- Comment #2 from Ian Balchin <inksi at fables.co.za> ---
Whooooah!

I am not sure that I read you correctly.

I don't want to achieve case-insensitive searching at the expense of
case-sensitive searching. If that is the case I wish I had not
mentioned it <sob>. I have plenty of reasons to use case-sensitive searching in
my database.

I do not have knowledge of the underlying Kexi structures, but I
realise that Kexi has to have some point where it checks the SQL
query written by the user for validity and this would be more
complex where a given sql product may not use a function that another
product does. ie. Kexi concentrates on core functions common to
supported databases.

It looks like ILIKE falls into the category of a non-ansi-standard
postgresql extension? But LIKE is ANSI standard.

I do prefer writing my own queries. That said why does the failure of an
SQL check have to prejudice the acceptance of a hand-written sql query -
especially when the aim of Kexi is to have the user design the query
graphically and to whom the SQL window will be a mystery best left alone.

In any case, someone using SQLite is not likely to latch onto the ILIKE query,
and if they do can this actually break anything? Will SQLite not just return
its own error message?

It seems to me that case in searching is a very basic requirement. Every
search box in every application has a tick-box for that - even the kexi Find
box (which
searches the data in memory of course). However implemented users will surely
expect this as a given?

Am I barking up the wrong tree here? Feel free to put me right with
some tuition or references.

Ian

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