Version based database migration with Liquibase 

Thank you for the video. One comment I would like to make is that all videos about Liquidbase or Flyway talk about benefits of automatic migration. And this is clear. But what they all fail to explain is handling of different environments such as PROD, TEST, DEV, etc. Also release dates. So, while explanation on how to setup and use the tools seem to be all over the net, there is little to none touching on these topic but they are very important as for example in large enterprises, we ad developers mostly dont even get a view of real database and have zero access rights to it. So, how would the tool has the rights to access it? How should it handle different environments such as PROD, TEST, DEV etc? What about release dates? etc...

So can Liquibase generate the XML files with the new schema automatically?

Very good video for newbies with Liquibase. Txs!!

could you please suggest how rollback works, I have tried rollback with tag but it's not working fo rme

Interesting tutorial, thank you very much for the infos. We are waiting for more....

I think changesets are unique on basis of Author name + id+ changelog file classpath. Please correct me if wrong.

Hi thanks for the introduction. Can you please show how to update dB on startup using spring boot and gradle? Thanks.

Nice video. Can i use liquibase for store procedures, triggers etc. If you have document or video please share.