Chat now with support
Chat mit Support

SQL Navigator for Oracle 7.4 - User Guide

Quick Overview Working With SQL Navigator Navigation Oracle Logon Code Editor Visual Object Editors Team Coding and Version Control Systems Modules, Windows And Dialogs
Analyze Tool Auto Describe Tool Benchmark Factory Bookmarks Dialog Capture Web Output Change Logon Password Dialog Code Analysis Code Assistant Code Road Map Code Templates Code Test Database Source Code Search Dialog DB Navigator Describe Difference Viewer Edit Data ER Diagram Explain Plan Tool Export Table Find and Replace Dialog Find objects Dialog Find Recycle Bin Objects Dialog Formatting Options HTML Viewer Import HTML as PL/SQL Import Table Java Manager Job Scheduler Locate In Tree Output Window PL/SQL Profiler Profile Manager Project Manager Publish Java to PL/SQL Quick Browse Rename Object Search Knowledge Xpert Select DB Object Dialog Server Output Server Side Installation Wizard Session Browser Source Preview SQL Modeler SQL Optimizer Task Manager Web Support Configuration Dialog Wrap Code
View | Preferences About Us

Configure Concurrent Version Systems (CVS)

Team Coding and Version Control Systems > Configure Team Coding > Configure Concurrent Version Systems (CVS)

These configuration settings are specific to Concurrent Version Settings (CVS).

  1. From the Main Menu, click Team Coding | Configure.

  1. Select Concurrent Version Systems (CVS) | Settings

 

Setting

Description
CVS Executable

Specify the name of the CVS program file in one of the following ways:

  • Specify the full path to the file, such as C:\Program Files\CVS\cvs.exe. This forces SQL Navigator to use the specified program.
  • Specify only the file name, rather than the entire path (the location of the program file must be in your system path). SQL Navigator will use the first occurrence it finds of the specified file name.

Global Options

Specify any global options that you want SQL Navigator to pass to CVS whenever a CVS command is executed by SQL Navigator. For example, the default option of -f tells CVS to ignore your .cvsrc options file.

You can use more than one option. Separate multiple options with a space.

Note: Do NOT enter a -d CVSROOT option here. SQL Navigator adds this option automatically, using the CVSROOT you provide in the CVS Login window.

Dates and Times in CVS Output

Description

Date Format

These options specify how CVS will send dates. You can use the following formats:

d

Day as a number without a leading zero (1-31)

dd

Day as a number with a leading zero (01-31)

m

Month as a number without a leading zero (1-12)

mm

Month as a number with a leading zero (01-12)

yy

Year as a two-digit number (00-99)

yyyy

Year as a four-digit number (0000-9999)

Default: yyyymmdd

Time Format

These options specify how CVS will send times. You can use the following formats:

h

Hour without a leading zero (0-23)

hh

Hour with a leading zero (00-23)

n

Minute without a leading zero (0-59)

nn

Minute with a leading zero (00-59)

s

Second without a leading zero (0-59)

ss

Second with a leading zero (00-59)

Default: hhnnss

Time Zone

Direct SQL Navigator to adjust the time stamps read from the output of CVS commands. For example, to subtract eight hours from all timestamps, specify a value of -800. To add three hours, enter a value of 300.

Default: 0

Login

Description

Login Automatically

Omit a prompt when SQL Navigator logs into CVS after connecting to the database. The most recently used CVSRoot will be used.

To use this option, the following must be true:

  • The Team Coding option "Disable Login Prompt on Connection" must not be enabled.
  • The TC=NO command-line option must not be enabled.

  • You previously logged in to CVS from SQL Navigator and:

    The previous login used an authentication method that did not require a password

    or

    You checked the Save Password option on the login form.

Time Between Keypresses

Set the amount of time (in milliseconds) that SQL Navigator pauses after sending each character of the password to the CVS password prompt.

The default is zero.

Note: If you find that CVS is returning "invalid password" errors, you may need to increase this number. A suggested figure is 100 milliseconds.

 

Configure Git

Team Coding and Version Control Systems > Configure Team Coding > Configure Git

These configuration settings are specific to git.

  1. From the Main Menu, click Team Coding | Configure.

  1. Select git | Settings

 

Setting Description
Git Client

Point to a different Git executable. Typically, no change is required in this field.

Automatically Login to Default Git Repository

Direct SQL Navigator to log in to the default repository without opening the login window.

Allow SQL Navigator Login to Update Repository User and Email Direct SQL Navigator to update the Git user and email configuration settings for the repository. These are used to track the author of changes and commits.
Commit Comments

Set the default comment for commits if no comment is made by the user during the commit. Git requires comments for commits.

 

Configure IBM Rational ClearCase

Team Coding and Version Control Systems > Configure Team Coding > Configure IBM Rational ClearCase

Note: SQL Navigator requires that you already have the IBM Rational ClearCase Client installed, a valid ClearCase license, and the capability to run the ClearTool Command line.

These configuration settings are specific to IBM Rational ClearCase.

  1. From the Main Menu, click Team Coding | Configure.

  1. Select IBM Rational ClearCase | Settings

 

Setting Description
ClearCase Executable Select the ClearCase executable file that you want to use.
Validate Validate that SQL Navigator can launch the selected executable.
Automatically load Views and VOBs from ClearCase Server Automatically load ClearCase views and versioned objects from the specified hosts when SQL Navigator starts.
Reserve/unreserve on checkout/checkin Use ClearCase reserved checkout.
Force Comments on Check in Force the inclusion of comments upon check-in of code.

 

Configure Perforce (P4)

Team Coding and Version Control Systems > Configure Team Coding > Configure Perforce (P4)

These configuration settings are specific to Perforce.

  1. From the Main Menu, click Team Coding | Configure.

  1. Select Perforce (P4) | Settings

 

General tab

Setting Version
Server Name Specify the server for the Perforce repository.
Server Port Specify the access port on the sever where Perforce is set up (default is 1666).
Client Locate the path to the Perforce command line executable (P4.exe).

Options tab

Setting Version

Connection

Set the following connection options:

Automatically connect to default Perforce client workspace

Performs automatic logon to the default workspace when logging in to Perforce.

Automatically load workspaces from P4 server

  • If this option is set, SQL Navigator checks the Perforce server for client workspace information when logging on to Perforce.
  • If this option is not set, Perforce checks for saved workspace information on the client desktop. (Deselect this option if Perforce loads slowly when you log in.)

Only load server workspaces for logon user

Only loads workspaces belonging to the logged-on user in the list of Perforce workspace loaded from the server. Select this option if you need to reduce the load time at logon.

File Locking

Use locking during checkin /checkout

Locks files upon check in or check out.

 

Verwandte Dokumente

The document was helpful.

Bewertung auswählen

I easily found the information I needed.

Bewertung auswählen