<div>Hi stackers!</div><div><br></div><div>I noticed, that tables in database use two database engines instead of two, but model descriptions does not override __table_args__ = {'mysql_engine': 'InnoDB'}.</div>



<div>This is design decision or migration_repo bug, or something else?</div><div><br></div><div>mysql> select table_name, table_type, engine FROM information_schema.tables;</div><div>+---------------------------------------+-------------+--------+</div>



<div>| table_name                            | table_type  | engine |</div><div>+---------------------------------------+-------------+--------+</div><div>   .... system tables here ....</div><div>| agent_builds                          | BASE TABLE  | MyISAM |</div>



<div>| auth_tokens                           | BASE TABLE  | InnoDB |</div><div>| block_device_mapping                  | BASE TABLE  | MyISAM |</div><div>| certificates                          | BASE TABLE  | InnoDB |</div>



<div>| compute_nodes                         | BASE TABLE  | InnoDB |</div><div>| console_pools                         | BASE TABLE  | InnoDB |</div><div>| consoles                              | BASE TABLE  | InnoDB |</div>



<div>| export_devices                        | BASE TABLE  | InnoDB |</div><div>| fixed_ips                             | BASE TABLE  | InnoDB |</div><div>| floating_ips                          | BASE TABLE  | InnoDB |</div>



<div>| instance_actions                      | BASE TABLE  | InnoDB |</div><div>| instance_metadata                     | BASE TABLE  | InnoDB |</div><div>| instance_type_extra_specs             | BASE TABLE  | MyISAM |</div>



<div>| instance_types                        | BASE TABLE  | InnoDB |</div><div>| instances                             | BASE TABLE  | InnoDB |</div><div>| iscsi_targets                         | BASE TABLE  | InnoDB |</div>



<div>| key_pairs                             | BASE TABLE  | InnoDB |</div><div>| migrate_version                       | BASE TABLE  | InnoDB |</div><div>| migrations                            | BASE TABLE  | InnoDB |</div>



<div>| networks                              | BASE TABLE  | InnoDB |</div><div>| projects                              | BASE TABLE  | InnoDB |</div><div>| provider_fw_rules                     | BASE TABLE  | MyISAM |</div>



<div>| quotas                                | BASE TABLE  | InnoDB |</div><div>| security_group_instance_association   | BASE TABLE  | InnoDB |</div><div>| security_group_rules                  | BASE TABLE  | InnoDB |</div>



<div>| security_groups                       | BASE TABLE  | InnoDB |</div><div>| services                              | BASE TABLE  | InnoDB |</div><div>| snapshots                             | BASE TABLE  | InnoDB |</div>



<div>| user_project_association              | BASE TABLE  | InnoDB |</div><div>| user_project_role_association         | BASE TABLE  | InnoDB |</div><div>| user_role_association                 | BASE TABLE  | InnoDB |</div>



<div>| users                                 | BASE TABLE  | InnoDB |</div><div>| virtual_interfaces                    | BASE TABLE  | InnoDB |</div><div>| virtual_storage_arrays                | BASE TABLE  | MyISAM |</div>



<div>| volume_metadata                       | BASE TABLE  | MyISAM |</div><div>| volume_type_extra_specs               | BASE TABLE  | MyISAM |</div><div>| volume_types                          | BASE TABLE  | MyISAM |</div>



<div>| volumes                               | BASE TABLE  | InnoDB |</div><div>| zones                                 | BASE TABLE  | InnoDB |</div><div>+---------------------------------------+-------------+--------+</div>



<div><br></div>