Neat and clear, perfect video for me. Thank you!

mute this background music please

Can u pls provide code repo

ewww. XML

that music tho

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

Does this still work since the Hub is not accepting new data or registrations? And also, is it only available for Pro users? Thanks.

So, what does Liquibase do??

annoying music , presenting using his wife's profile in the browser ! what is this ? amataure hour?!

#UM

How about packages, procedures, schedulers, etc., is liquibase compatible with this part of Oracle DB?

This is exactly how developers work, sa account and messing around with Master database... was that difficult to create a new database and avoid all these bad practises??? Liquibase must be a miracle... :)

The poor keyboard is taking a real pummeling.

The music detracts from an otherwise good video.

kill the background music

if I upgrade Liquibase be 4.27.0 what happen on DBCLH because my previous version have no that table. Is it possible to retroact activities history?

What is the command used in actions to generate report?

Good to see this table showing the history.

Finally Liquibase updated their website with some cool UI. Glad to Experience it

do we have an example of liquibase and docker-compose ?

Where I can find the documentation on how to do this with docker compose? I'm currently facing issues when passing the changelog.xml file

Hi. How to restore table backup files using Liquibase command or settings please?

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

I don't understand how you connected to sql without placing any database.

How do I start a project from scratch to add changes? Or how do I add this to a project?

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 ?

music adds absolutely no value to this besides making me comment on how bad it is

Please remove the music

Good video but the music is too loud

Hi @liquibase can you create a playlist for folks who are getting started with liquibase? Thanks in advance!

More of these please 🙂

I have a question. If changelog doesn't change anything in the tables( assume we use if not exists condition, and the corresponding insert lines not executed), will it still record changeset id in databaselog though the changeset is no-op?

Hello. I have a doubt. The commands "db.collection.insertMany" how do I transform it into xml in the video pattern?

Congrats 🎉

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.

Nice

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

I believe this video does not cover an important caveat. The above solution only works if there are no DDL statements between the production hotfix and latest development branch. Consider this, the PROD 3.0 creates a table. In QA 3.0.1 there was a DDL to change a column name of the table. Now In 3.0.HF1 for PROD there is an insert statement using the old column name. Once 3.0.3 reaches QA, it would run the changeset from 3.0.HF1 as well as 3.0.3 . However the insert statements from 3.0.HF1 changeset would fail since in QA 3.0.1 already changed the column name. Although 3.0.3 would have a proper insert statement equivalent to 3.0.HF1, there should be a way to make sure that the actual changeset from 3.0.HF1 does not execute in a database that already applied changesets from 3.0.1 . Liquibase supports this via pre conditions that are not discussed in this video. The pre condition for 3.0.HF1 should be that the changelog table does not have an entry later than 3.0 . This ensures that the changeset from 3.0.HF1 does not execute on QA and DEV, but the equivalent changeset from 3.0.3 executes correctly. Further, the insert statements from 3.0.3 should have proper conflict clauses to make sure that it is re-runnable. This will be applicable when a database with say 2.10 upgrades all the way to 3.0.3. In that case 3.0.HF1 would run the insert statements and 3.0.3 would have a duplicate insert that must be auto resolved with a conflict clause. If there is a better way to accomplish this, please do let us know.

Getting error while migrating data in mongo “can not decode a subtype 3 (uuid legacy) bson binary when the decoder is configured to use the standard uuid representation. Can you please help.

Where is the repo ???

Thanks for this tutorial. Can I Integrate aws DynamoDB with Liquibase ?

watched whole video and still have no idea what liquidbase does

Hello. Could you tell me, how to avoid generation unique name of trigger? Is it possible?

𝐩𝐫𝐨𝐦𝐨𝐬𝐦

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

bad video why not explain all docker command in details

Please get a Microphone not close to the keyboard - typing is awful - otherwise great video

is it possible to setup liquibase for an existing project that's been developed a lot?

I think u missed explaining the changelogLOCK collection as well. please explain whats the difference of that with the changelog one.. tnx!

Thanks for this neat tutorial. I loved your way of teaching and showing the case. Amazing!