Bug #72900 Properly initialize db option hash table
Submitted: 6 Jun 2014 16:32 Modified: 10 Jun 2014 21:37
Reporter: Ramil Kalimullin Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Server: Charsets Severity:S3 (Non-critical)
Version:5.6 OS:Any
Assigned to: Ramil Kalimullin CPU Architecture:Any

[6 Jun 2014 16:32] Ramil Kalimullin 
Description:
Correct "dboptions" hash table initialization taking in account "lower_case_table_names".

How to repeat:
Code inspection.
[10 Jun 2014 21:37] Paul DuBois 
Noted in 5.7.5 changelog.

The server did not take the lower_case_table_names value into account
in determining the database directory from which to read the db.opts
file, and thus could read the file from an incorrect directory.