Git and DB state

Question

Git is excellent tool: you could switch to the one of previous versions and bisect the history to locate the bug.

But actually you could not, because when you're switching to the old release, your DB remains in its most recent state, so your Web app won't work at all.

Is there any common solution on how to work around that?

Some thoughts:

• I can't add the entire DB into every commit
• I can't use migration back and forward, because I'm losing data in back migrations. The data is not a part of the structure, but it is handy for debug.
• And of course, I need something to be in sync with Git (a hook?), otherwise I'm getting extra time expenses which are not well.

Answer 1

try this tool

https://hub.docker.com/r/arelis/gitdb

its a version control to mysql and use git for control version

Answer 2

The cleanest solution would be having a script that creates a database with dummy/testing data. Since this script and your database structure would be versioned, it would always create the correct one.

However, you cannot automatically perform a back-migration since the information about structure changes happening after the current commit are not available.