Summary: | Search and escaping of database wildcard characters in filenames | ||
---|---|---|---|
Product: | [Applications] digikam | Reporter: | Quincy <bbc.quincy> |
Component: | Searches-Advanced | Assignee: | Digikam Developers <digikam-bugs-null> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | metzpinguin |
Priority: | NOR | ||
Version: | 7.1.0 | ||
Target Milestone: | --- | ||
Platform: | Microsoft Windows | ||
OS: | Microsoft Windows | ||
Latest Commit: | https://invent.kde.org/graphics/digikam/commit/5e87ffe78349f56a6da3f8ddee62095074d725ff | Version Fixed In: | 7.2.0 |
Sentry Crash Report: |
Description
Quincy
2020-12-08 11:51:45 UTC
The search works when I search for "\_270\_" (without quotation marks). Maik Ok, it works with MySQL but not with SQLite. Maik Git commit 5e87ffe78349f56a6da3f8ddee62095074d725ff by Maik Qualmann. Committed on 08/12/2020 at 19:32. Pushed by mqualmann into branch 'master'. add escape character '\' to LIKE search with SQLite FIXED-IN: 7.2.0 M +2 -1 NEWS M +12 -1 core/libs/database/item/query/fieldquerybuilder.cpp https://invent.kde.org/graphics/digikam/commit/5e87ffe78349f56a6da3f8ddee62095074d725ff Thanks for the quick fix. So the wildcards "_" and "%" will still be usable and have to be escaped if one needs to use them as literal? Could one please update the documentation accordingly as wildcards may be of nice use, but I think most people will try "*" and "?" otherwise if at all. |