Changing the version control method
Two version control methods are available, the lock method and the merge method.
Notes:
- In the lock method, you check out an object, preventing others from working on it, then you check it back in when you have finished.
- In the merge method, you work on an object, commit your changes, then resolve any conflicts caused by other users working on the same object at the same time.
- Version control applies only to certain object types, and the object types are different depending on which version control method is in use.
- Changing the version control method affects only objects that are created after the change. Existing objects continue to be controlled by the method that was in use when they were created.
- Because it is possible to swap between version control methods at any time, within the same model group you can have objects of the same type under different version control methods.
To change the version control method that applies to new objects:
- Select File | Master database settings and look at the Use merge version control option.
If there is a tick against the option, the merge method is in use. If there is no tick against the option, the lock method is in use.
- If you want to change the version control method that will apply to new objects, select Use merge version control.
When you are copying within databases, you have the option convert an entire database or model group to use the merge version control. Refer to Copy within databases and convert to merge model for details.
