If you describe the workflow for the production DB, then yes, that's exacly how it works. But we also need a way to fiddle with the dev environment, while keep

If you describe the workflow for the production DB, then yes, that's exacly how it works. But we also need a way to fiddle with the dev environment, while keeping track of everything that happened during development phase and making sure that it can be applied to the production DB in a single command with little room for errors. Having a git repo in sync with the DB and a full history of changes in commit log helps a lot.