Best Practices for Managing Liquibase Changelogs

[@ironcobra83]

how can I manage the situation of a single database with different projects that are using it. Not only microservices but even other old applications? All of that are using the same database

[@LBaralgeen]

Does Liquibase merge all db changes for a single table in final snapshot? or it will be a chain of changes for every table?

[@MarkStatkus]

Are you manually managing this root change log? I can't find a single bit of info how it's created thru CLI, managed or referenced as you execute further CLI commands. More context on the site, blogs, etc helpful. Chicken or egg stuff I guess. Mainly, if I do a initial generate changelog and create a root, its not setup like this. And if I try to create the base XML for root, then reference it it says it already exists. Feels like a trap. And one that I wouldn't think would be set 30 years after relational databases have existed.

[@VictorRamirez-hr7yj]

hi, where can I get the slides? some words get hidden by the presenters windows

[@hitesharyal3146]

We have master branch in git. we cut release branch change id:author (for stored procedure) and then deploy. and after successful deployment merge it to master. how to handle rollback ? like if something bad happen during release deployment and want to run master. we won't be able to do so because master change sets already present in DBCHANGELOG table. how to handle without deleting entries from DBCHANGELOG table ?

[@陈俏锋]

very nice video! how to manage the changelog files when team code with microservice ?

[@hoanghahuy7933]

Ideally, each team has their own microservice, and each microservice has its own database. So now get back to the video..

[@vasudevansivalingam8494]

create index if not exists department_index on department using btree (department_id); How can I create a Liquibase changeset for the above Postgresql? I have to use "using btree" feature in order to attain the desired performance,

[@liquibase7511]

Hey Vasudevan! Thank you for reaching out with your comment. If you have questions like these the best place to share them is on our community forum at forum.liquibase.com.

[@vasudevansivalingam8494]

create index if not exists employee_index on employee(emp_id, (emp_first_name|| ' ' ||emp_last_name)); I'm able to use the above statement in Postgres, I want to have it in my Liquibase changeset. I need to combine the first and last names as above in the index since it gives better performance. I was told that I can't deviate from it.

[@liquibase7511]

Hey Vasudevan! Thank you for reaching out with your comment. If you have questions like these the best place to share them is on our community forum at forum.liquibase.com.

[@EldorJ10]

Great video!

[@liquibase7511]

Thanks!

[@koderkev42]

#UM