Currently the table that keeps track of the already migrated Elastic migrations has no primary key defined in the schema.
This can be required in MySQL through sql_require_primary_key and is not always configurable by the end user (e.g. DigitalOcean enforces this on their managed database solution).
This PR adds a primary key to that table so the table can be created.
Currently the table that keeps track of the already migrated Elastic migrations has no primary key defined in the schema. This can be required in MySQL through
sql_require_primary_key
and is not always configurable by the end user (e.g. DigitalOcean enforces this on their managed database solution).This PR adds a primary key to that table so the table can be created.