This model allows developers to work on their local copy of the database and commit changes to a centralized repository.
When you link a database to source control with the help of the Studio, a local copy of the database is not automatically created. Therefore, you must create it manually either on your local computer or on the remote one.
Firstly, all developers install dbForge Studio for MySQL on their machines so that they can all commit their changes. Then, any of them needs to link the database to version control and make the initial commit. During this step, it is required to specify the dedicated model mode. Subsequently, other developers can get the latest version of the committed database using one of the following methods:
Once all the developers have linked their copies of the database to the repository, the workflow is as follows:
It is recommended to get the latest database version before you start working on changes. This should be done to prevent conflicts with others’ modifications.
The repository contains all changes made to the database objects. For more information about the changes history, see View Source Control history.
The changes made to the same object by several developers may lead to a conflict. For more information about how to resolve conflicts, see Resolve conflicts.
Developers must maintain databases on their individual machines, which might be considered a drawback in terms of management and resources.