Trying to reproduce bug reported in 324134 and create documentation for that. Using a test directory I copied 4 existing pictures in it, left one as is(1), one suffix was changed (uppercase, 2), one renamed entirely (3), last (4) renamed as previous but difference in capitalisation (digikambug1.1 and digikambug1.2). On opening digikam, only 1,2 and 4 were shown/recognised (digikambug1.3). The advanced rename was done (digikambug1.4), result was both as expected (reproduce 32414) where 4 disappeared (and 2 surprisingly not), and unexpected because 3 reappeared (digikambug1.5). In digkam1.dbg and digikam2.dbg is the output from traces as set by kdebugdialog. In digikam1.log is the mysql log from executed statements. Reproducible: Always Steps to Reproduce: Refer to description Actual Results: As described Expected Results: 1) Digikam should have recognised the 4 initial pictures in the album. 2) On rename all 4 pictures should still be there. As highlighted in 324134, you can recover the apparent lost images by running fixing (?) queries against the database.
Created attachment 95732 [details] digikam1.2 initial list of files picture view This is the contents of the test directory.
Created attachment 95733 [details] digikambug1.1 Initial file list
Created attachment 95734 [details] digikam1.3 Digikams initial view of the album, one is missing.
Created attachment 95735 [details] digikambug1.4 Rename the pictures
Created attachment 95736 [details] digikambug1.5 Result of rename, one disappeared, one missing showed up
Created attachment 95737 [details] digikam1.dbg Debug log 1 from kdebugdialog
Created attachment 95738 [details] digikam2.dbg digikam debug log 2 from kdebugdialog.
Created attachment 95739 [details] digikam1.log MYSQL log from this test run.
We need to make sure that the MySQL schema for text fields specifies a collation value that compares strings in a case sensitive manner. Useful background information at http://dev.mysql.com/doc/refman/5.7/en/case-sensitivity.html I suspect that we should be using the utf8_bin collation. http://dev.mysql.com/doc/refman/5.7/en/charset-charsets.html
MySQL has been made case sensitive. It now uses utf8_bin collation. Try digiKam 5.0.0 version.
This file is closed now. Feel free to reopen, with necessary updates, if you still face the issue.