Summary: | SCAN : Search for new items does not recognize modified tags in sidecar files | ||
---|---|---|---|
Product: | [Applications] digikam | Reporter: | web.paul.v.l |
Component: | Database-Scan | Assignee: | Digikam Developers <digikam-bugs-null> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | caulier.gilles |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Mint (Debian based) | ||
OS: | Linux | ||
Latest Commit: | https://commits.kde.org/digikam/9c77203fdc10cd59aa0ba645ab3fde7f774dbaf2 | Version Fixed In: | 6.0.0 |
Description
web.paul.v.l
2014-09-23 22:47:04 UTC
You must use "Maintenance/Sync Metadata and Database" tool with the right direction. This take a while. This is why these operations are not present in scan for new items process. Gilles Caulier I understand that "On 24/09/14 03:09 AM, Gilles Caulier wrote:". I know it is not in the "new items", for one reason to much time. I have surmised that the "Maintenance/Sync Metadata and Database" options of either updating sidecars or updating the database does so without checking for anything other than the existence of a sidecar or an entry in the database. That is the database writes every entry out to a sidecar or every sidecar is read and entered into the database "one way only". I have not noted in this process any means of checking between database and sidecars for modified/changes to tags. Unless I have missed something this lack of checking is why the process takes so long. It is that length of time as an outcome of the current process that I see as a problem. One possible way to speed that up would be to time stamp, sidecars and tag entries. I mention only tags for this is of critical interest to me. On 24/09/14 03:09 AM, Gilles Caulier wrote: > https://bugs.kde.org/show_bug.cgi?id=339342 > > Gilles Caulier <caulier.gilles@gmail.com> changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > CC| |caulier.gilles@gmail.com > > --- Comment #1 from Gilles Caulier <caulier.gilles@gmail.com> --- > You must use "Maintenance/Sync Metadata and Database" tool with the right > direction. > > This take a while. This is why these operations are not present in scan for new > items process. > > Gilles Caulier > (In reply to Gilles Caulier from comment #1) > You must use "Maintenance/Sync Metadata and Database" tool with the right > direction. > > This take a while. This is why these operations are not present in scan for > new items process. > > Gilles Caulier Can you reproduce the problem using digiKam Linux AppImage bundle ? The last bundle is available at this url: https://drive.google.com/drive/folders/0BzeiVr-byqt5Y0tIRWVWelRJenM Gilles Caulier What's about this file using 5.8.0 pre-release buncle : https://files.kde.org/digikam/ Thanks in advance Gilles Caulier Git commit 9c77203fdc10cd59aa0ba645ab3fde7f774dbaf2 by Maik Qualmann. Committed on 13/09/2018 at 19:47. Pushed by mqualmann into branch 'master'. store as modification date always the most recent from the image or the sidecar Related: bug 397340, bug 398331, bug 380341 FIXED-IN: 6.0.0 M +5 -2 NEWS M +14 -1 core/libs/database/collection/collectionscanner.cpp M +14 -1 core/libs/database/item/imagescanner.cpp https://commits.kde.org/digikam/9c77203fdc10cd59aa0ba645ab3fde7f774dbaf2 |