The specific reason should be that the creation of primary key is repeated in these two places, multi_cluster_sync_info table.
When I delete one of them, I find that the error will still be reported. It is the error of the index that is too long,still the multi_cluster_sync_info table.
mysql5.5:Under the innodb engine, we can start innodb_large_Prefix parameter to extend the length of a single index to 3072 bytes (but the length of a joint index is still limited to 3072 bytes).
mysql8.0:the innodb_large_prefix parameter is deprecated,The default is 3072 bytes.
repeated primary key in multi_cluster_sync_info can not create table while using mysql,this is a difference between mysql and h2db, we will fix this bug later;
after fix repeated primary key, the error whie creating table in mysql is timestamp must set default value, this is another difference between mysql and h2db;
after fix two problem, we test it in mysql5.7 and mysql:latest, it work well;
Describe the bug
Use
create_Table.sql
failed to build the database,The specific reason should be that the creation of primary key is repeated in these two places,
multi_cluster_sync_info
table.When I delete one of them, I find that the error will still be reported. It is the error of the index that is too long,still the
multi_cluster_sync_info
table.So should we consider prefix index or reconsider the creation of index
Environment