Feature request #2970

Unify query builders

Added by Alister Hood about 10 years ago. Updated about 10 years ago.

Status:Closed
Priority:Low
Assignee:nobody -
Category:Build/Install
Pull Request or Patch supplied: Resolution:fixed
Easy fix?:No Copied to github as #:13030

Description

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 :)

Associated revisions

Revision 2019d63b
Added by Jürgen Fischer about 10 years ago

add lower/upper support to search string (fixes #2970)

git-svn-id: http://svn.osgeo.org/qgis/trunk/[email protected] c8812cc2-4d05-0410-92ff-de0c093fc19c

Revision d2cb8b28
Added by Jürgen Fischer about 10 years ago

add lower/upper support to search string (fixes #2970)

git-svn-id: http://svn.osgeo.org/qgis/[email protected] c8812cc2-4d05-0410-92ff-de0c093fc19c

History

#1 Updated by Borys Jurgiel about 10 years ago

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.

#2 Updated by Jürgen Fischer about 10 years ago

  • Resolution set to fixed
  • Status changed from Open to Closed

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

Replying to [comment:1 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.

#3 Updated by Borys Jurgiel about 10 years ago

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?

#4 Updated by Jürgen Fischer about 10 years ago

Replying to [comment:3 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 1cbad878 (SVN r14157). Therefore some disabled buttons could be enabled.

#5 Updated by Borys Jurgiel about 10 years ago

Thanks! It's perfect now :)

#6 Updated by Alister Hood about 10 years ago

Thanks, that sounds good.

Replying to [comment:2 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?

#7 Updated by Jürgen Fischer about 10 years ago

Replying to [comment:6 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).

Also available in: Atom PDF