Experience with database version control framework

Hi Tech researchers,

Again, I came up with one more scenario from my POC experience, and as per the title, I guess you may have understood what I will discuss today.

I worked for a big telecom operator from India. For them, we prepared a web application and a customised RFID device for reading tags.

Before giving a demo to clients, we did a trail run in our office a few times on the day of the presentation. We went from the office to home because everything was running smoothly. But my manager found one issue in the application, and that caused a big problem while scanning the RFID tag. So he requested one of the associates on the team and asked her to fix the issue.

She discovered the source of the problem, resolved it, and demonstrated the solution and outcome to the manager. The fix has been pushed to the repo.

However, the application failed during the demo.

The team began investigating why the application had failed, as well as recent check-ins, server status, and so on. But I discovered that the problem was that she had made changes to a database table on her local machine, but the old table structure remained on the server. That is the primary cause of the application’s failure.

At that time, I didn’t know what the solution was for those types of issues. But after joining a new organization, I heard the term “Liquibase” for the first time.

So I started looking into it, and then I realised we’d be dealing with the above problem statement using Liquibase or a database version control framework.

Conclusion: Experience matters.