Bug 408788 - Empty Search result -> reset -> nonempty search result
Summary: Empty Search result -> reset -> nonempty search result
Status: RESOLVED FIXED
Alias: None
Product: digikam
Classification: Applications
Component: Searches-Advanced (other bugs)
Version First Reported In: 5.9.0
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-06-16 15:48 UTC by Christian Gruber
Modified: 2022-01-08 15:37 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In: 7.5.0
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Christian Gruber 2019-06-16 15:48:46 UTC
Sometimes, when I perform an advanced search, I get no results. When I look through all search items, nothing strikes me. When I then perform a reset, and enter my search criteria again, I suddenly get the expected result. So there must be a hidden search parameter.
Can all the used search criteria been shown? It is not unlikely that there is an additional hidden one.
Comment 1 Maik Qualmann 2019-06-16 19:21:29 UTC
There are a lot of search fields, because something can be overlooked. It would help, if the problem arises, to post the search query printed in the console to get a clue.

Maik
Comment 2 Christian Gruber 2019-06-17 09:43:41 UTC
I did not know that a search string is built. But it is not written to my console (perhaps because I have 'QT_LOGGING_RULES="*=false"' to reduce the debugging garbage). But since it is already created, it could be not only printed on the console, but accessed otherwise, for example by a menu entry, or in the results window etc.
Comment 3 caulier.gilles 2019-06-17 17:11:35 UTC
Yes, please activate the Qt debug statements on the console. The "String" is in face an XML container used to encapsulate the database queries.

Gilles Caulier
Comment 4 griffiths_andy 2020-05-31 16:25:17 UTC
I have seen this occasionally when setting up a new search. I know it's anecdotal but I'll try and get some logging the next time it happens to me.

What generally happens is that something like the picture height or width have been set to unfeasible small values, maybe by accidentally touching the scroll wheel while hovering over the field.

For me, I think part of the problem is that I expect the 'Advanced Search' button to open up a new, reset search, whereas it does not always. For example I just tried it and it carried over the album selection from my last query, but not the date selection I was using.

Of course, doing a reset will sort this.

Maybe the 'Advanced search' button should implement 'new' advanced search? The only other implementation of new advanced search would seem to be in right click menu of an existing search. This is not obvious at first.
Comment 5 caulier.gilles 2020-07-31 12:59:37 UTC
digiKam 7.0.0 stable release is now published:

https://www.digikam.org/news/2020-07-19-7.0.0_release_announcement/

We need a fresh feedback on this file using this version.

Best Regards

Gilles Caulier
Comment 6 caulier.gilles 2022-01-08 11:16:07 UTC
Maik,  what do you think about the proposal in comment #4 ? It can be a solution to prevent a confusion when user want to create a new search and edit an existing one. 

Gilles
Comment 7 Maik Qualmann 2022-01-08 15:37:25 UTC
Git commit b9c4b0e7f04d34bd3ccc6dd60d2d47298b8a1c3d by Maik Qualmann.
Committed on 08/01/2022 at 15:36.
Pushed by mqualmann into branch 'master'.

separate buttons for new and edit Advanced Search
Related: bug 431774
FIXED-IN: 7.5.0

M  +2    -2    NEWS
M  +24   -9    core/utilities/searchwindow/searchtabheader.cpp
M  +2    -1    core/utilities/searchwindow/searchtabheader.h

https://invent.kde.org/graphics/digikam/commit/b9c4b0e7f04d34bd3ccc6dd60d2d47298b8a1c3d