Unify query builders

[Alister]

Queries are currently case sensitive e.g. if you search for CNAME = 'Massey' it won't find objects with CNAME = 'MASSEY'

It would be good if query's could be case insensitive instead. This could perhaps be optional, although I imagine most people would prefer the option on most of the time :)

[borysiasty]

Use a common query builder for filtering layer features and selecting features. I.e. add Save/Load button to the former and ILIKE button to the latter.

[jef]

added lower() and upper() in r14154. You can use upper(CNAME)='MASSEY' now (just like in postgres or spatialite).

Replying to borysiasty:

Use a common query builder for filtering layer features and selecting features. I.e. add Save/Load button to the former and ILIKE button to the latter.

The queries are implemented differently. The search query builder uses the internal search string processor and operates independently from the provider.

The "normal" query builder sets the layers subset string and operates on provider level.

[borysiasty]

I'm just proposing to add the ILIKE functionality to the search query builder. The upper(CNAME) LIKE 'MASS%' is a bit inconvenient. Is there any reason to not keeping such ticket open?

[jef]

Replying to borysiasty:

I'm just proposing to add the ILIKE functionality to the search query builder. The upper(CNAME) LIKE 'MASS%' is a bit inconvenient. Is there any reason to not keeping such ticket open?

You just changed the description while I was busy fixing it - the original bug.

ILIKE, IN and NOT IN added in r14156. Therefore some disabled buttons could be enabled.

[borysiasty]

Thanks! It's perfect now :)

[Alister]

Thanks, that sounds good.

Replying to jef:

The queries are implemented differently. The search query builder uses the internal search string processor and operates independently from the provider.

The "normal" query builder sets the layers subset string and operates on provider level.

What does this actually mean? Are the capabilities of the "normal" query builder different depending on the provider?

[jef]

Replying to Alister:

The "normal" query builder sets the layers subset string and operates on provider level.

What does this actually mean? Are the capabilities of the "normal" query builder different depending on the provider?

Yes. You can enter whatever queries the provider supports (eg. rather complex where clauses for the postgis or spatialite case).