[Digikam-devel] [Bug 268204] MySQL filenames are case-INsensitive

[Daniel Bauer]

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





--- Comment #6 from Daniel Bauer <linux daniel-bauer com>  2011-03-17 20:30:37 ---
Hi Marcel, thanks for the info about the album = NULL, so I just ignore that...

> We use UTF8 everywhere internally and never latin1. Maybe something went wrong
> during import/export?

I've done several tests with several database collation settings. I always
added a new folder in digikam and imported the images from a folder on my
desktop. 

Whenever the table "images" (or just the field "name") had COLLATE=utf8_bin
digikam didn't show the correct file-name for a file called
"img_123_oberkörper.jpg" allthough the file was correctly saved in the
database. In digikam album the image was replaced by the placeholder-image,
clicking on it gave "could not load images" (or alike..) and renaming the file
within digikam also did not work...

A "SELECT FROM images WHERE name LIKE '%oberk%'" gave the correct results.
Don't know what happens within digikam...

Please try to import a file "nö.jpg" while collation for "name" is set to
utf8_bin and see if you can reproduce...

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.