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

--- Comment #2 from John Dickson <jmdick...@gmail.com> ---
Yeah, adding the binary operator to the queries would not be a good idea. Not
only do you end up with full table scans, but also issues if you take an ISO
8859-1/latin1 string with non-ASCII characters and try to compare that to a
column containing utf-8 values.

mysql> SELECT table_schema, table_name, table_collation FROM
information_schema.tables where table_schema like '%digikam%';
+--------------------+----------------------+-------------------+
| table_schema       | table_name           | table_collation   |
+--------------------+----------------------+-------------------+
| digikam            | AlbumRoots           | utf8_general_ci   |
| digikam            | Albums               | utf8_general_ci   |
| digikam            | DownloadHistory      | latin1_swedish_ci |
| digikam            | ImageComments        | latin1_swedish_ci |
| digikam            | ImageCopyright       | latin1_swedish_ci |
| digikam            | ImageHistory         | latin1_swedish_ci |
| digikam            | ImageInformation     | latin1_swedish_ci |
| digikam            | ImageMetadata        | latin1_swedish_ci |
| digikam            | ImagePositions       | latin1_swedish_ci |
| digikam            | ImageProperties      | latin1_swedish_ci |
| digikam            | ImageRelations       | latin1_swedish_ci |
| digikam            | ImageTagProperties   | latin1_swedish_ci |
| digikam            | ImageTags            | latin1_swedish_ci |
| digikam            | Images               | latin1_swedish_ci |
| digikam            | Searches             | latin1_swedish_ci |
| digikam            | Settings             | latin1_swedish_ci |
| digikam            | TagProperties        | latin1_swedish_ci |
| digikam            | Tags                 | latin1_swedish_ci |
| digikam            | TagsTree             | NULL              |
| digikam            | VideoMetadata        | latin1_swedish_ci |
| faces_digikam      | FaceMatrices         | latin1_swedish_ci |
| faces_digikam      | FaceSettings         | latin1_swedish_ci |
| faces_digikam      | Identities           | latin1_swedish_ci |
| faces_digikam      | IdentityAttributes   | latin1_swedish_ci |
| faces_digikam      | OpenCVLBPHRecognizer | latin1_swedish_ci |
| faces_digikam      | OpenCVLBPHistograms  | latin1_swedish_ci |
| similarity_digikam | ImageHaarMatrix      | latin1_swedish_ci |
| similarity_digikam | ImageSimilarity      | latin1_swedish_ci |
| similarity_digikam | SimilaritySettings   | latin1_swedish_ci |
| thumbnails_digikam | CustomIdentifiers    | latin1_swedish_ci |
| thumbnails_digikam | FilePaths            | latin1_swedish_ci |
| thumbnails_digikam | ThumbSettings        | latin1_swedish_ci |
| thumbnails_digikam | Thumbnails           | latin1_swedish_ci |
| thumbnails_digikam | UniqueHashes         | latin1_swedish_ci |
+--------------------+----------------------+-------------------+
34 rows in set (0.00 sec)

Is the application logic dependent on case insensitive behavior of Albums,
AlbumRoots, and Images tables? If not, setting the collation of those to
utf8_general_cs would be a better approach.

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to