サポートと今すぐチャット
サポートとのチャット

SQL Navigator for Oracle 7.4 - Installation Notes

Team Coding Settings

The Team Coding global settings control the Team Coding environment at the database level. These settings apply to all Team Coding users.

To work with these settings go to Team Coding | Administer, then select the Settings tab.

VCS

(Optional) Select a VCS to use for Team Coding. Then, click to set VCS settings.

Note: When a user with the TC_ADMIN_ROLE sets up a VCS, SQL Navigator stores the server settings as the default for all Team Coding users. This feature only works with Concurrent Versions System (CVS), Microsoft Team Foundation Server (TFS) and Visual Source Safe, Perforce, IBM Rational ClearCase, and Subversion (SVN). See the directions for your chosen VCS:

Concurrent Version Systems (CVS) Configuration Options

Git Configuration

IBM Rational ClearCase Configuration

Microsoft Team Foundation Server Configuration Options

Perforce Configuration Options

Serena PVCS Version Manager Options

Subversion Configuration Options

(Not required for Microsoft Visual Source Safe.)

Force check-in comment

Require users to enter a comment when checking in an object.

Force check-out comment

Require users to enter a comment when checking out an object.

Force new revision on check-in

Force the VCS to create a new revision record when checking in an object, even if the object source is unchanged. Note: Some version-control systems do not support this feature and will not create a new revision for unchanged objects.

Remove source from VCS when deleting an object

When an object that is controlled by a Team Project is deleted in SQL Navigator, delete the object from the VCS.

Select Prompt before removing to prompt users before removing the object.

When differences in source versions exist...

When you open an object or script, Team Coding compares it with the latest revision in the version control system (VCS) repository (unless it is checked out, in which case SQL Navigator opens a read-only version of the file). If the database object or script differs from the version saved in the VCS, SQL Navigator notifies you. Differences in objects could be due to a number of factors. For example, another tool or a script may have been used to edit the object, or the archive in the VCS may have been updated by some means other than Team Coding.

You can choose one of the following options to resolve the difference:

Open Database Version: Always load the database version in read-only mode.

Open VCS Version: Always update the database with the version from the VCS repository and load it in read-only mode. Caution: Opening the version from the repository will cause the object in the database to be updated.

Prompt User: Prompt the user to choose between opening the database version or the VCS version.

 

関連ドキュメント

The document was helpful.

評価を選択

I easily found the information I needed.

評価を選択