MySQL inconsistently altering name of indexes associated with foreign keys on InnoDB tables
By : Tyronusana
Date : October 16 2020, 06:10 PM
Hope this helps I have noticed the same thing, but I've never seen any official documentation that explains this. I agree it seems like InnoDB "knows" which indexes were created implicitly and which were created explicitly. But I don't know where it tracks this information. InnoDB exposes much of the metadata in INFORMATION_SCHEMA tables, but it must store more information in the internal data dictionary.
Is it possible to use Mysql foreign keys in InnoDB tables for inverse lookup?
By : Maria C. Calixto
Date : March 29 2020, 07:55 AM
this one helps. I wonder if it is possible to use FK's in Mysql (InnoDB) for inverse lookup. , After reading up a lot, one option would be to use something like:
referenced_table_name IS NOT NULL
Row locking in MySql InnoDb with foreign key constraints and indexes applied?