The Need For Database Developers
A large number of revision-control systems exist and are used for Development source Control and database developers can use a large number of revision-control systems. The majority are centralised, and based on the library or repository model, and based on CVS. These use the concept of check-out and check-in and rely on file or module locking to prevent clashes. Database developers can work on various processes which can help to get an exclusive write-access to a module. The source control system that database developers provide can write access and can update the source so as to make the changes available to all co-workers. This process is usually atomic and it either succeeds entirety or is rolled-back.This method of revision control with the help of database developers and it is easy to subvert this method.
The database developers using version-merging, which attempts to deal with simultaneous edits by merging the results of the edits of different developers and a more subtle approach can be provided. This works well, and creates less distraction for developers, until several people work on the same code, at which point it can easily result in inconsistent code that does not compile or run. Distributed source control systems give database developer a local copy of the entire development history, and changes are copied from one such repository to another. These changes are imported as additional development branches, and can be merged in the same way as a locally developed branch. Based on the histories of the common ancestors, or merit of previous changes, and users are informed if a merge is impossible and merging in many of these systems can be extremely sophisticated.
Database developers need to have a private version of the current database for doing the bulk of their development work, but they will need to be able to access a shared database that is built from the definitive source in source control for testing with realistic data sets and creating test data, and for making make ‘uncontrolled’ experimental changes that are overwritten from the master source in source control. It should be impossible to check in source directly from this shared database.