使用maven和postgres-db运行liquibase的问题 [英] problem running liquibase with maven and postgres-db

问题描述

在postgresql-db上运行maven的liquibase-plugin时出现问题。
当试图从命令行运行liquibase：update时，我收到错误消息

I have a problem running maven's liquibase-plugin on a postgresql-db. When trying to run liquibase:update from the command-line, I get the error message

[ERROR] Failed to execute goal org.liquibase:liquibase-plugin:1.9.5.0:update (de
fault-cli) on project backend-persistence: Error setting up or running Liquibase
: liquibase.exception.JDBCException: Error executing SQL CREATE TABLE databasech
angeloglock (ID INT NOT NULL, LOCKED BOOLEAN NOT NULL, LOCKGRANTED TIMESTAMP WIT
H TIME ZONE, LOCKEDBY VARCHAR(255), CONSTRAINT PK_DATABASECHANGELOGLOCK PRIMARY
KEY (ID)): FEHLER: Relation ╗databasechangeloglock½ existiert bereits -> [Help 1
]

简单地删除db-table没有帮助， liquibase正在创建它两次，如日志文件所示：

simply dropping the db-table does not help, it looks like liquibase is creating it twice, as the logfile suggests:

...
CREATE TABLE databasechangeloglock (ID INT NOT NULL, LOCKED BOOLEAN NOT NULL, LOCKGRANTED TIMESTAMP WITH TIME ZONE, LOCKEDBY VARCHAR(255), CONSTRAINT PK_DATABASECHANGELOGLOCK PRIMARY KEY (ID))
COMMIT
BEGIN
INSERT INTO databasechangeloglock (ID, LOCKED) VALUES (1, false)
COMMIT
BEGIN
LECT NULL AS TABLE_CAT, n.nspname AS TABLE_SCHEM, c.relname AS TABLE_NAME,  CASE n.nspname 

....
CREATE TABLE databasechangeloglock (ID INT NOT NULL, LOCKED BOOLEAN NOT NULL, LOCKGRANTED TIMESTAMP WITH TIME ZONE, LOCKEDBY VARCHAR(255), CONSTRAINT PK_DATABASECHANGELOGLOCK PRIMARY KEY (ID))
FEHLER:  Relation »databasechangeloglock« existiert bereits (already exists)

任何想法如何解决这个问题？

Any ideas how to solve this problem?

提前感谢，

Matthias

推荐答案

您可能在您的postgres数据库中有多个模式。要解决您的问题，请移动公共模式中的所有数据。

You're probably have multiple schema in your postgres database. To solve your problem, move all your data in the public schema.

这篇关于使用maven和postgres-db运行liquibase的问题的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！