#46553Resolve issues with case-sensitive files
Description
Currently, the handling of file-name casing is improperly defined: The database will usually be case-insensitive (for MySQL this is the default), but we cannot be sure if the filesystem supports case-sensitivity. This leads to a multitude of problems, as the edge-cases are not considered in the code.
We first have to check if we want to support case-sensitivity at all. If not,- case-sensitive file systems have to be taken care of in the driver (which might require quite some work for all comparisons etc.) and
- we have to make sure the database is always case-insensitive.
- the file system might still not support it, so we have to cope with that (i.e., check if a file with the same name, but different casing exists before adding a file)
- the database always has to be case-sensitive (or we have to store SHA1/MD5 hashes of name and identifier and compare against these)
Oracle and PostgreSQL seem to have case-sensitivity as the default, while MySQL is case-insensitive by default (for sensitivity the collation of the column has to be changed to utf8_bin).
Reviews 1
Related issues 5
- Bug #43027Problems on case-sensitive filesystems
- Feature #44991DB table COLLATION: disabled for ext_tables.sql but not for ext_tables_static+adt.sql
- Bug #45504Case sensitive filenames lead to file list problems
- Bug #53575Language module: Wrong argument passed to File::updateProperties()
- Task #53604CleanUp Canonicalize and Unique Identifier in Drivers