Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Don't force lowercase for custom field column names
Custom field names are referenced by name in columns definitions. There were some conversions in place to compare column names by converting to lowercase. However, the field name is stored in custom fields table without any conversion. This causes: - The configured columns array can be inconsistent with the available columns names. - When the database uses case sensitive matching, the columns are not shown properly and are presented as not existant. So given that custom field names are already stored with unrestricted names, which include spaces and non-alphanumeric characters, forcing them to lowercase while treating them is not a significant requirement at the moment. Fixes: #17367, #20248
- Loading branch information