Version Control

From RapidSQL
Jump to: navigation, search

Go Up to Project Management

Version control archives files and tracks changes to files over time. With an integrated version control, you can easily track changes to database objects.

Version control addresses the following issues:

  • Team Development By controlling access to a file so that only one person at a time can modify, it prevents accidental replacement or loss of another user's changes.
  • Version Tracking By archiving and tracking versions of source code files, you can to retrieve them if necessary, thereby effectively creating files so that source code can be reused.
  • Safety By adding database object scripts and files, it creates backups in case of loss, thereby ensuring a recovered version of source code.

When you create a project, you can immediately place the project into version control or you can Create a New Project From a Version Control Project. You can also add projects and files to version control later selecting Project menu, Version Control and Add To Version Control....

Version Control Integration

To use integrated version control features, you must have the version control client software installed on the same computer, or the MSSCCI plug-in for the selected Version Control System. You must select the appropriate version control on the Version Control Tab of the Option Editor.

Rapid SQL supports all Version Control Systems compatible with MSSCCI. Other Version Control Systems not compatible with MSSCCI may work under certain conditions.

Note: 64 bit versions of Rapid SQL can now use 32 bit MSSCCI providers by choosing to do so in the version control option page. Most providers are 32 bits only, so this allows users to continue to use the 64 bit version of our application even if the have a source control that has no 64 bit provider available.

Version Control Configuration

Information about how to configure a Version Control system is described in Version Control Options.

Using Version Control

Once you add a file or project to the version control, most functions found in the underlying version control system are available directly. Basic version control procedures include:

Note: Version control functionality depends on your underlying version control system. For more information on version control procedures, consult the documentation included with your version control system.

Version Control Icons

The table below describes the icons related to Version Control files:

Icon Description

VCicon01.png

File is not checked out by anyone.

VCicon02.png

File is checked out non-exclusively and only by the user logged into source control.

VCicon03.png

File is checked out non-exclusively only by a one user who is not the user logged into source control.

VCicon04.png

File is checked out exclusively and only by the user logged in to source control.

VCicon05.png

File is checked out exclusively and only by a user who is not the user logged in to source control.

VCicon06.png

File is checked out by multiple users, including the user logged in to source control.

VCicon07.png

File is checked out by multiple users, not including the user logged in to source control.

VCicon08.png

Project file is not checked out by anyone.

VCicon09.png

Project file is checked out non-exclusively and only by the user logged into source control.

VCicon10.png

File is checked out non-exclusively only by a one user who is not the user logged into source control.

VCicon11.png

Project file is checked out exclusively and only by the user logged in to source control.

VCicon12.png

Project file is checked out exclusively and only by a user who is not the user logged in to source control.

VCicon13.png

Project file is checked out by multiple users, including the user logged in to source control.

VCicon14.png

Project file is checked out by multiple users, not including the user logged in to source control.

Topics

Personal tools