Comment 2 for bug 1109131

This seems to be a collation problem within the database. Only binary fields are handled case-sensitive by MySQL when selecting records.

Could you please check the collation of your database, the table "tx_dlf_structures" and the field "tx_dlf_structures.index_name"?

Does this bug occur even if you use binary collations like "utf8_bin"?