Bug 297296 - Support regular Expression and boolean operators in search tool
Summary: Support regular Expression and boolean operators in search tool
Status: REPORTED
Alias: None
Product: digikam
Classification: Applications
Component: Searches-Advanced (show other bugs)
Version: 2.8.0
Platform: unspecified Linux
: NOR wishlist
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
: 153208 268979 (view as bug list)
Depends on:
Blocks:
 
Reported: 2012-04-02 08:42 UTC by julien.t43+kde
Modified: 2024-11-20 21:05 UTC (History)
6 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description julien.t43+kde 2012-04-02 08:42:42 UTC 
It would be very cool to be able to use boolean operator, regexp, gmail-like operators (has:attachement in:read ...) in searches or in filters.
For now, there is no way to do (at least in one search):
- search one-star hotel with neither legend, neither title
- search zero-star pictures with non-empty legend or title
- search in fulltext (anywhere) a location and a word
- looking for empty or not-empty metadata field
Comment 1 julien.t43+kde 2012-07-07 00:30:11 UTC 
No feedback here ?

Would really like to have query like "(rate:1+ OR tag=~/plan/i) OR cybershot"
Some engines here (not sure if fit for digikam but ...): http://www.mediawiki.org/wiki/Fulltext_search_engines
Comment 2 julien.t43+kde 2012-10-20 17:32:22 UTC 
still not possible to search "((!tag1 and rate=1) or tag=~/tag[234]/)".
digikam 2.8.0 from linux ppa/lubuntu.

seems related:
Bug 153208 - Option to search for empty/not empty or regular expressions for text fields in advanced search
Bug 218312 - make search results exlude tags childrens 
Bug 183425 - advanced search filter by tags - "meet all..." does not work
Comment 3 caulier.gilles 2015-05-16 13:48:17 UTC 
*** Bug 268979 has been marked as a duplicate of this bug. ***
Comment 4 caulier.gilles 2015-05-16 13:48:37 UTC 
*** Bug 153208 has been marked as a duplicate of this bug. ***