![]() ![]() | 1 | agilliland | migrations/001_initial_schema.json | 08:45:43 | 1 | EXECUTED | 7:1b0742414a26a9b52ed5622ce7516ad7 | createTable tableName=core_organization createTable tableName=core_user createTable tableName=core_userorgperm addUniqueConstraint constraintName=idx_unique_user_id_organization_id, tableName=core_userorgperm createIndex indexName=idx_userorgp. | ID | AUTHOR | FILENAME | DATEEXECUTED | ORDEREXECUTED | EXECTYPE | MD5SUM | DESCRIPTION | COMMENTS | TAG | LIQUIBASE | CONTEXTS | LABELS | DEPLOYMENT_ID | The records seems to be created several years ago when we used v0.22.2, I checked the database the table DATABASECHANGELOG exists, How can I do upgrade database manually without data lost from v0.22.2 to v0.40.2, I see some comments in the output sqls, such as "- Added 0.25.0", shall I execute the sqls since v0.23.2 so that the upgrade will be OK and which sqls should I run? It seems that some sqls can't be executed which setup before v0.22.2 I set MB_DB_AUTOMIGRATE to false and got all the sqls to execute manually and see the sql to create table such as "core_user" or "core_organization". ![]() Using external database, mysql version 5.7.16, Liquibase version: 3.6.3 Error: (conn=1492291) Table 'core_organization' already exists Error: (conn=1492291) Table 'core_user' already existsĮRROR changelog.ChangeSet :: Change Set migrations/000_migrations.yaml::1::agilliland failed. I'm trying to upgrade metabase from v0.22.2 to v0.40.2, but the database migration showed error and the container exited,ĮRROR changelog.ChangeSet :: Change Set migrations/000_migrations.yaml::1::agilliland failed.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |