Quantcast
Channel: Liquibase Forums
Viewing all articles
Browse latest Browse all 2993

Re : There is already an object named 'DATABASECHANGELOGLOCK' in the database when i update

$
0
0
Hi all,

I just ran into the same problem using liquibase 3.1.0, while using 3.0.8 works. I attached a ZIP file containing a ready-to-run unit test demonstrating the issue (unzip and 'mvn test' will suffice). An in-memory HSQLDB is created and a trivial changeset is applied successfully for 3.0.8.

In the pom.xml you can change liquibase versions from 3.0.8 to 3.1.0 by switching comments in lines 13 and 16. In the latter case liquibase will throw a java.sql.SQLException: Table already exists: DATABASECHANGELOGLOCK in statement [CREATE TABLE PUBLIC.DATABASECHANGELOGLOCK].

I am aware that reporting issues directly in JIRA is preferred way, however I am not 100% sure if I did everything correct while using the Liquibase Core Java API. A Hibernate entity manager over HSQLDB 1.8 is encapsulating the connection object I am using to initialize the liquibase object and I hope this does not contribute to the issue. 


Thanks and regards

Kay

Viewing all articles
Browse latest Browse all 2993

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>