https://bugs.kde.org/show_bug.cgi?id=414344
Maik Qualmann changed:
What|Removed |Added
Version Fixed In||7.5.0
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=414344
Maik Qualmann changed:
What|Removed |Added
Latest Commit||https://invent.kde.org/grap
https://bugs.kde.org/show_bug.cgi?id=414344
Maik Qualmann changed:
What|Removed |Added
CC||k...@forum.titlis.org
--- Comment #8 from Maik
https://bugs.kde.org/show_bug.cgi?id=414344
Maik Qualmann changed:
What|Removed |Added
CC||p.r.worr...@gmail.com
--- Comment #7 from Maik
https://bugs.kde.org/show_bug.cgi?id=414344
--- Comment #6 from Maik Qualmann ---
Yes, "utf8_general_ci" is known to be case insensitive. We are planning a major
change to the tags table for MySQL. In this context we can switch to "utf8_bin"
for paths. This change will only be made with
https://bugs.kde.org/show_bug.cgi?id=414344
--- Comment #5 from John Dickson ---
The situation is the same with 7.0.0. Here is what I observe with the 7.0.0
appimage:
If two files in the same subdirectory have names that only differ by the case
of one or more characters, only one is displayed
https://bugs.kde.org/show_bug.cgi?id=414344
caulier.gil...@gmail.com changed:
What|Removed |Added
CC||caulier.gil...@gmail.com
--- Comment
https://bugs.kde.org/show_bug.cgi?id=414344
Maik Qualmann changed:
What|Removed |Added
Component|Database-Scan |Database-Mysql
--- Comment #3 from Maik
https://bugs.kde.org/show_bug.cgi?id=414344
--- Comment #2 from John Dickson ---
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
https://bugs.kde.org/show_bug.cgi?id=414344
Maik Qualmann changed:
What|Removed |Added
CC||metzping...@gmail.com
--- Comment #1 from Maik
10 matches
Mail list logo
