Chat now with support
Chat with 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

Using IBM Rational ClearCase

Team Coding and Version Control Systems > Provider logon > Using IBM Rational ClearCase

When you log on to Version Control or Team Coding, you will be asked to select the Clear Case View.

Mapped Drive and Views

ClearCase views are client views of ClearCase Versioned Objects (VOBS).

The ClearCase mapped drive is the folder created when ClearCase created the view. This drive contains the folders where your working files will be saved.

SQL Navigator lists all the views that you have installed on the local desktop. The view must be mapped to the project VOB used by SQL Navigator.

To log in to ClearCase

  • Select your ClearCase view on the ClearCase Login tab.
  • Select the Project VOB.

Note: SQL Navigator does not currently support saving working files to a separate folder. This is a read only value.

  • On the ClearCase Explorer tab, you can review the Project VOBs available in the ClearCase View.

When you select a Project VOB from Source Control, SQL Navigator will show a list of the controlled project folders within the selected VOB. This version of SQL Navigator only supports a single level of folders within a ClearCase Project VOB.

 

Version Control Systems

More about IBM Rational ClearCase and SQL Navigator

Check in and Check out

Team Coding and Version Control Systems > Check in and Check out

The check-in and check-out of objects that are controlled in Team Coding or the VCS can be done in different ways in SQL Navigator.

Check in/check out individual objects

The Check In and Check Out buttons in Team Coding Manager can be used for both database objects and files.

When you check out an object or file, it locks that item in the database. The item remains locked until you check in your changes through Team Coding. You must check out an object before you can compile it.

If a VCS is being used, there are two parts to a checkout

  1. Check out the source from the VCS.
  2. Create a check-out transaction for the object in Team Coding. This is what determines the state of the object in DB Navigator or Team Coding Manager.

If a VCS is not being used with Team Coding, only step 2 from the preceding actions occurs. Team Coding does nothing with your source code in this case.

To check individual items in and out

  1. Open the script or select the object in the .
  2. Click to check out an object or click to check in an object.

You can also check in or check out an object by right-clicking it in DB Navigator or Team Projects browser, and then selecting the desired command.

Check in all items

To check in all objects at the same time, you can:

  • Click on the Team Coding Manager toolbar.
  • Select Team Coding | Check-in all to open a dialog where you can select objects individually from a list.

If a VCS is being used, there are two parts to a checkin:

  1. Check in the source to the VCS.
  2. Create a check-in transaction for the object in Team Coding. This is what determines the state of the object in DB Navigator or Team Coding Manager.

If a VCS is not being used with Team Coding, only step 2 from the preceding actions occurs. Team Coding does nothing with your source code in this case.

Automatic Check In and Check Out

You can have SQL Navigator automatically check in an item when you open it and check out an item when you close it. You can also have SQL Navigator prompt you to enter a comment. For more information, see Configure Team Coding.

Undo a checkout

To cancel the check out and reverse any changes, click on the Team Coding Manager Toolbar. Alternatively, you can right-click the object then select Undo check-out.

 

Version Control Systems

Team Coding and Version Control Systems > Version Control Systems

You can use a version control system (VCS) in conjunction with Team Coding to control files and database objects. SQL Navigator provides direct support to specific third-party version control systems and it also provides SCC support to connect to additional version control systems. You must have Team Coding installed to work with a VCS through SQL Navigator.

Important: Quest Software is unable to provide support for source control issues caused by the version control system, including the version control system's support for Microsoft's SCC API. If you have problems connecting to Toad through SCC, contact the version control system's Support.

 

Direct Supported

Version Control System Version
Concurrent Versions System (CVS)*

CVS 1.11.9 and later

CVSNT 2.08 and later

For more information, see Concurrent Version (CVS) System Requirements.

Git     *

A git client for Windows must be installed.

For more information, see More about Git and SQL Navigator.

IBM Rational ClearCase      *

Version 7.1 for Windows.

ClearTool command line is required.

For more information, see More about IBM Rational ClearCase and SQL Navigator.

Note: You must set up a working client view, mapped to the Project VOB on the client computer, before using it in SQL Navigator.

Perforce       *

2010.2 (command-line client)

For more information, see More about Perforce and SQL Navigator.

Note: The Perforce client must match your operating system. For example, if you are running Windows 7 64-bit, then you must use the 64-bit Perforce client.

Serena PVCS         *

5.2 and later

Note: PVCS 6.6.1 and 6.8.0 are specifically not supported with Team Coding.

Serena PVCS Version Manager:

  • PVCS is supported with Team Coding for both 32-bit and 64-bit SQL Navigator.
  • It has been tested with Serena PVCS Version Manager 8.5/ 8.4, and replaces existing Merant PVCS interfaces.
  • PVCS Version manager Command Line Interface (CLI) is supported.
  • PVCS Command Line option must be included when installing PVCS

Apache Subversion (SVN)*

1.6.5 and later

Microsoft Team Foundation Server

2005 through 2013

For more information, see More about Team Foundation Server and SQL Navigator.

Microsoft Visual SourceSafe

5.0, 6.0, and 2005 (8.0)

*These version control systems connect using a command-line client.

 

SCC Support

In addition to providing direct support to the version control systems, SQL Navigator supports additional version control systems through Microsoft's SCC API. You should be able to connect to any version control system that uses SCC.

To connect to a version control system using SCC, you must install the system's SCC-compliant client. See the system's documentation for instructions on how to install their SCC client.

Note: It is strongly recommended you use the native APIs for SourceSafe and PVCS when using Team Coding (instead of the SCC integration).

Most version control systems that integrate with SQL Navigator through the SCC API ignore the "Force revision" flag and the "Create a new revision for existing objects" option when exporting.

Concurrent Version Systems (CVS) Requirements

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

To use Concurrent Version Systems (CVS) with Team Coding, you need to have a CVS command-line client installed on your system. The following minimum versions are recommended:

  • CVS client version 1.11.9 or later
  • CVSNT client version 2.08 or later

Team Coding has been tested with the following clients:

  • CVS clients 1.11.9 and 1.11.17 with the pserver authentication
  • CVS client 1.11.12 with pserver and ssh authentication
  • CVSNT clients 2.0.8 and 2.0.41a with the pserver authentication
  • CVSNT clients 2.0.11, 2.0.26, 2.0.34, and 2.0.41 with sserver, pserver, and sspi authentications
  • CVSNT client 2.0.14 with sserver, pserver, sspi, ssh, ext, and local authentications
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating