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

Re : Is switching SQL Server databases during a liquibase changeset and the subsequent unreleased lock a bug?

$
0
0
Thanks Steve,

The actual fix for me was that I had to remove the "use" statement altogether. It was a schoolboy cut and paste error that it was in there in the first place. 

However, I'm not sure I agree that it isn't a bug. The fact that liquibase reports "Successfully released change log lock" when blatantly no lock had been set on database_b, and the original lock is left in place on database_a surely isn't right?. However, I didn't just raise a Jira straight away, as I wanted to canvas opinions such as these first, thanks!

Viewing all articles
Browse latest Browse all 2993

Trending Articles



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