Ilya Pekelny ba6705a731 Explicit foreign key indexes. ... Overview: MySQL requires indexes on foreign keys. Such an index is created on the referencing table automatically if it does not exist. Motivation: MySQL names foreign keys indexes differently dependent from itself version. Implicit fk indexes is MySQL specific behavior, so it should be ignored during comparision. We plan to use Alembic to compare models and migrations I0758c7e09d1d46ce870c3f94f76c2a177955e143. Alembic doesn't support 5.5 naming convention. So we need consistent index name for all MySQL versions to be easily ignored. Solution: A new migration script renames incorrectly named fk indexes on MySQL. Reproduction: Stop execution when foregn keys will be initialized. See schema with your MySQL shell client. With 5.5, indexes which was not named explicitly, will have a name such as <tablename>_<columnname>_fk, with 5.1 it will be <columnname>. Change-Id: I01ba0c8856afbda59394395ac319bf83a55ee2be Partial-Bug: #1292591		2014-04-24 16:25:48 +03:00
..
__init__.py	Remove copyright from empty files	2014-02-13 17:35:11 +08:00
001_add_oauth_tables.py	Remove vim header	2014-02-08 23:54:04 +08:00
002_fix_oauth_tables_fk.py	Remove vim header	2014-02-08 23:54:04 +08:00
003_consumer_description_nullalbe.py	Remove vim header	2014-02-08 23:54:04 +08:00
004_request_token_roles_nullable.py	oauth1 extension migration fails with DB2	2014-02-25 11:29:50 -06:00
005_consumer_id_index.py	Explicit foreign key indexes.	2014-04-24 16:25:48 +03:00