unknown 2dde698e0e Bug#55222 - RB://517 - Approved by Sunny ... InnoDB does not attempt to handle lower_case_table_names == 2 when looking up foreign table names and referenced table name. It turned that server variable into a boolean and ignored the possibility of it being '2'. The setting lower_case_table_names == 2 means that it should be stored and displayed in mixed case as given, but compared internally in lower case. Normally the server deals with this since it stores table names. But InnoDB stores referential constraints for the server, so it needs to keep track of both lower case and given names. This solution creates two table name pointers for each foreign and referenced table name. One to display the name, and one to look it up. Both pointers point to the same allocated string unless this setting is 2. So the overhead added is not too much. Two functions are created in dict0mem.c to populate the ..._lookup versions of these pointers. Both dict_mem_foreign_table_name_lookup_set() and dict_mem_referenced_table_name_lookup_set() are called 5 times each.		2010-11-30 12:25:52 -06:00
..
srv0srv.c	Bug#55222 - RB://517 - Approved by Sunny	2010-11-30 12:25:52 -06:00
srv0start.c	Make output from innobase_start_or_create_for_mysql() consistent	2010-11-29 14:53:09 +02:00