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

[Marcel Wiesweg]

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





--- Comment #5 from Marcel Wiesweg <marcel wiesweg gmx de>  2011-03-17 19:49:46 ---

> Marcel, do we need to update the database schema to version 7 or can I extend
> the current (version 6) schema definition (since the gsoc is not official
> released).

I would really like to avoid incrementing the schema for this, unless really
necessary. Is it possible to solve via ALTER TABLE statements? Then we'd have a
workaround for existing MySQL users.

> I have no problems when using latin1 collation and charset on the filed "name":

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

> why does field "album" allow NULL?

Information about deleted images is kept for some time, then the album is null.
If you moved photos from A to B, then scan first A then B, information would be
lost.

> As collation type I would sugest to use utf8_bin 

Weird that MySQL does not provide any utf8 _cs collations...

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