从使用mySQL启动Spring Boot时提供重复键名'JV_GLOBAL_ID_OWNER_ID_FK_IDX'的JAVER

Question

我正在尝试将Javers 5.9.0与我的Spring Boot 2.1.13应用程序集成到MySQL中。

当我运行我的应用程序时

java.lang.RuntimeException：java.sql.sqlSyntaxerRoreXception：重复的键名'jv_global_id_owner_id_fk_idx'

请找到完整的错误堆栈

Answer 1

在附近找到一份工作

1. 在application.yaml中进行以下更改SqlSchemaManagementEnabled:false。这将在应用程序启动时停止创建表
2. 手动创建表/索引。类似于

创建表javers.jv_commit(commit_pk BIGINT NOT NULL AUTO_INCREMENT,author VARCHAR(200),commit_date TIMESTAMP（3）,commit_date_instant VARCHAR(30),commit_id NUMERIC(22,2）,CONSTRAINT jv_commit_pk主键(commit_pk))ENGINE=innoDB；在gears_javers.jv_commit(commit_id)上创建索引jv_commit_commit_id_idx

创建表javers.jv_commit_property(property_name VARCHAR(191)NOT NULL，property_value VARCHAR(600)，commit_fk BIGINT，约束jv_commit_property_pk主键(commit_fk,property_name)，约束jv_commit_property_commit_fk外键(commit_fk)引用gears_javers.jv_commit(commit_pk))引擎=InnoDB

在gears_javers.jv_commit_property上创建索引jv_commit_property(commit_fk)在gears_javers.jv_commit_property上创建索引jv_commit_property_property_name_property_value_idx（property_name,property_value(191))

创建表javers.jv_global_id(global_id_pk BIGINT NOT NULL AUTO_INCREMENT,local_id VARCHAR(191),fragment VARCHAR(200),type_name VARCHAR(200),owner_id_fk BIGINT,CONSTRAINT jv_global_id_pk主键(global_id_pk),CONSTRAINT jv_global_id_owner_id_fk外键(owner_id_fk)引用gears_javers.jv_global_id(global_id_pk))引擎=InnoDB

在gears_javers.jv_global_id(local_id)上创建索引jv_global_id_local_id_idx；在gears_javers.jv_global_id(owner_id_fk)上创建索引jv_global_id_owner_id_fk_idx；

创建表javers.jv_snapshot(snapshot_pk BIGINT NOT NULL AUTO_INCREMENT,type VARCHAR(200),version BIGINT,state TEXT,changed_properties TEXT,managed_type VARCHAR(200),global_id_fk BIGINT,commit_fk BIGINT,CONSTRAINT jv_snapshot_pk主键(snapshot_pk),CONSTRAINT jv_snapshot_global_id_fk外键(global_id_fk)引用gears_javers.jv_global_id_fk

在gears_javers.jv_snapshot(global_id_fk)上创建索引jv_snapshot_global_id_fk_idx；在gears_javers.jv_snapshot(commit_fk)上创建索引jv_snapshot_commit_fk_idx；在gears_javers.jv_global_id(owner_id_fk)上创建索引jv_snapshot_owner_id_fk_idx；