I was using the 3.1.1 Maven Liquibase Plugin (I’ve since upgraded to 3.2.0 and still have the same problem) with SQL Server, and ran into an issue where the liquibase lock was not released due to a change of databases in the middle of a changeset.
The scenario was this:
- Liquibase runs and successfully acquires the lock (say in database_a)
- <span when that clearly isn't true.
If someone can confirm whether they agree this is a bug or not, and I’ll raise a Jira