[digikam] [Bug 324134] New: Images disappear after advanced rename

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=324134

Gerard Dirkse <[hidden email]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[hidden email]

--- Comment #14 from Gerard Dirkse <[hidden email]> ---
Just hit this problem on 4.6.0, after renaming files in a folder (wanted the
suffix to be lower case), only images left in the album are the ones that were
lowercase to start with, from all other images in the folder (with uppercase
suffix) have disappeared.  Entries are still in table 'Images', but no longer
in 'Imageinformation'.  Reread metadata or rescan does not bring information
back.  Please provide method for recovery from this bug.

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=324134

--- Comment #15 from Gerard Dirkse <[hidden email]> ---
Could this be a 'feature' of MYSQL trigger behaviour for trigger 'delete-image'
? This trigger removes information from various places, including
'Imageinformation', after a DELETE. on table 'Images';

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=324134

--- Comment #16 from Gerard Dirkse <[hidden email]> ---
Is the update of the image name implemented as a DELETE, then INSERT with same
imageid ?, rather then an UPDATE SET....

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=324134

--- Comment #17 from Gerard Dirkse <[hidden email]> ---
I have been able to recover the data in following way against the digikam
database:

CREATE TEMPORARY TABLE `orphans` SELECT DISTINCT `id` FROM `Images` WHERE `id`
NOT IN (SELECT `imageid` FROM `ImageInformation`);
DELETE from `Images` WHERE `id` in (SELECT * FROM `orphans`);

Then when digikam gets started again, images are recovered, not sure if this
process leaves rubbish or not, but it appears not.  Would be nice if a database
tool could do this, recover information that has been somehow lost.

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=324134

[hidden email] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[hidden email]

--- Comment #18 from [hidden email] ---
I have tried this several times and this issue is also reproducible in digiKam
Version 5.0.0-beta6

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=324134

[hidden email] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Version|4.5.0                       |5.0.0

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=324134

--- Comment #19 from Larx <[hidden email]> ---
I can confirm that the bug is still present in beta6 (MySQL). I had hoped that
the MySQL rewrite would have fixed this bug.
Makes MySQL unusable if you want to avoid data loss...

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=324134

--- Comment #20 from Larx <[hidden email]> ---
Maybe this is related to bug #357617: During batch rename of video files, I
encounter strange behaviour, e.g. Digikam tries to rename files it has already
renamed and so on. Is there some basic flaw in the batch rename logic
triggering errors under certain conditions?

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=324134

--- Comment #21 from Larx <[hidden email]> ---
Problem still present in 5.0b6: I simply cannot batch rename video files (not
only MTS, but some times also MP4) reliably. Sometimes Digikam renames a bunch
and then fails, often it tries to rename a file it has already renamed (and
therefore claims - rightly - that the file is not present). Sometimes the error
message stops the renaming process, sometimes the process goes on in the
background?!?! I simply don't understand the behaviour, it's consistent only
inasfar as that batch renaming video files fails.

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=324134

--- Comment #22 from Larx <[hidden email]> ---
Sorry, added the above comment to the wrong bug.

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=324134

--- Comment #23 from Larx <[hidden email]> ---
Additional observation which might be related:

Because of the missing pics after advanced rename, I DROPped the MySQL database
and started from scratch. Digikam crashed twice after that, but then it scanned
the collection anew.

Everything seemed to be fine, but then I noticed that some pictures where
missing. For my quite big collection I could  not look in every folder, but for
the examples I found it seemed as if files with the same name, but the same
extension in lower and upper case where missing (e.g. name.jpg and name.JPG). I
renamed these pics and restarted Digikam, again two crashes (?!), but
afterwards the missing pictures were there again. (As I said, only those
missing files I noticed and which I renamed, might be that there are more
missing...)

It might also be a problem with the MySQL database - in the beginning I had
"Collation" as type, which I changed to some UTF8-type for the second attempt.

However, something seems to be wrong concerning the file name handling.

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=324134

--- Comment #24 from [hidden email] ---
Larx,

To be sure that problem remain with Mysql DB interface only, can you check if
problem exist with a Sqlite database. The schema are not the same and SQlite
interface is more advanced than Mysql one...

Thanks in advance

Gilles Caulier

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=324134

--- Comment #25 from Larx <[hidden email]> ---
I filed the bug from comment 23 seperately, see #364131.

I will try with SQLite when I find the time, however, SQLite is for my real
life no option as it completely fails already for a familiy photo collection on
a network drive to be handled from three different computers (digikam startup
time especially on WLAN is to be measured in hours, a central MySQL server
takes less than a minute...)

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=324134

--- Comment #26 from [hidden email] ---
yes, but Sqlite is the complete DB backend currently. We want to be sure that
it work as expected.

We have a student working this summer on Mysql backend. Comparing both,
especially one as Sqlite give the expected results will help to finalize Mysql
interface.

Gilles Caulier

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=324134

Maik Qualmann <[hidden email]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |FIXED
   Version Fixed In|                            |5.0.0
             Status|UNCONFIRMED                 |RESOLVED
      Latest Commit|                            |http://commits.kde.org/digi
                   |                            |kam/d18903fa644affd5f2b3c27
                   |                            |5b2544a54a9d64782

--- Comment #27 from Maik Qualmann <[hidden email]> ---
Git commit d18903fa644affd5f2b3c275b2544a54a9d64782 by Maik Qualmann.
Committed on 02/07/2016 at 17:30.
Pushed by mqualmann into branch 'master'.

make MySQL text fields case-sensitive
FIXED-IN: 5.0.0

M  +1    -2    NEWS
M  +81   -37   data/database/dbconfig.xml.cmake.in
M  +4    -1    libs/database/coredb/coredbschemaupdater.cpp

http://commits.kde.org/digikam/d18903fa644affd5f2b3c275b2544a54a9d64782

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel