지금 지원 담당자와 채팅
지원 담당자와 채팅

SQL Navigator for Oracle 8.0 - 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

Team Coding Manager

Use the Team Coding Manager to manage and work with the objects that are controlled by Team Coding. The Team Coding Manager displays Team Coding status and controlled objects for the current active connection. You can use Team Coding Manager as a floating pane or dock it to the left-hand side of SQL Navigator.

To open or close the Team Coding Manager

  • From the Main Menu, select Team Coding | Team Coding Manager.

 

The Team Coding Manager includes these tabs:

  • Team Projects
  • VCS

Note: If nothing is displayed on these tabs, it means that Team Coding was disabled by a Team Coding Administrator.

 

VCS tab

If a Team Coding administrator linked Team Coding to a version control system (VCS), the Version Control tab (also known as the VCS Browser) provides a view of the Team Coding objects in their version control projects, as well as other non-controlled projects. The folders for projects that contain Team Coding objects are colored green to distinguish them from other projects.

The Team Coding-controlled objects are displayed in the browser with a green check mark , to distinguish them from other files under source control. When these objects are checked out, their locks are controlled in Team Coding and the internal Team Coding transaction table is updated.

Team Projects tab

The Team Projects tab (also known as the Team Coding Browser) lists all of the Team Projects that are configured for the connected database. Only objects that are controlled by Team Coding are visible from this view. When you check out an object from this tab, Team Coding locks it.

Work with Team Coding objects

To display revision history

  1. In either tab, select the object for which you want to view history.
  2. Click again in the right-hand portion of the highlighted name to expose an arrow.
  3. Click the arrow. The revision history popup is displayed.

To view summary information

» In either tab, hover the mouse over the name of an object to view its lock status and VCS information.

To work with and manage controlled objects

To perform an action on a controlled object, you select the object in either tab and then click the appropriate action in the Team Coding Manager toobar, or use the right-click menu within the Team Coding Manager window.

Note: You may need to customize the toolbar to display all of the available actions. Click the arrow at the end of the toolbar, then select Add or Remove Buttons.

Select an action from the toobar or the right-click menu. (Actions not appropriate for the current workflow are disabled.) See the following table for action descriptions.

Icon Action Description

(Disabled if a VCS is not being used)

Synchronize Changes

Synchronize differences between the version in the database and the version in the VCS. Select the objects that you want to synchronize.

Synchronize resolves the following issues:

  • Differences between the VCS source code and the object in the database. Any differences are resolved by the global setting of the "When differences in source versions exist" option in the Team Coding Administrator window (as configured by a Team Coding Administrator). If the option is set to Prompt User (user chooses between opening the database version or the VCS version) a non-administrator user can make that choice. Otherwise, either the database or VCS version is opened, depending on the global setting. See Set Team Coding Global Settings for more information.
  • Objects in the database but not in the VCS are added to the VCS.
  • Objects in the VCS but not in the database are added to the database.

(Disabled if a VCS is not being used)

Create New Revision in the VCS

Create a new revision in the VCS for all controlled objects. This action loads all of the objects for a Team Project into the Synchronize window. Select the ones for which you want to make a new revision.

Compile PL/SQL Objects in DB

Compile the selected object in the database.

Configure Team Coding Settings

Open the local user settings for this installation of SQL Navigator. For more information, see Configure Team Coding.

Administer Team Coding

Open the Team Coding Administration utility. For more information, see Administer Team Coding.

Team Coding Status

View the current state of the local Team Coding installation, the VCS (if being used), the Team Projects, Team Coding Settings, and other environmental information. For more information, see Team Coding Status.

(Disabled if a VCS is not being used)

 VCS Logon

Log on to the VCS.

 

Select VCS Project

  
 

Add File

  

Check out

Check out one or more objects. 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.

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.

Undo checkout

Cancel the checkout.

Check in

Check in one or more objects to the VCS.

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.

Check in all

Check in all objects that you currently have checked out in your local SQL Navigator environment.

Get latest revision

Retrieve the latest revision of the object from the VCS. The object is not checked out, and there are no changes made to the database.

 

Compare contents

Compare the VCS version of an object side by side with the version in the database. You can also compare revisions in the VCS by selecting the revision numbers that you want to compare in the VCS browser and then clicking Compare Contents. See Compare Files and Objects for more information.

Open

Open the object in the Editor or the DB Navigator. To open an object so that you can work on it in an editor, you must first check it out.

Delete Record

Delete the object source from Team Coding and Version Control (if allowed by the administrative settings.)

Filter

Filter the items on the screen.

Refresh

Refresh the view of the objects.

Expand/Collapse

Expand or collapse the nodes in the tree. Click the arrow for options.

Break Team Coding Lock

Break a Team Coding lock created by another user. (Can only be performed by a Team Coding Administrator.)

Freeze

Freeze an object to prevent updates to it. (Can only be performed by a Team Coding Administrator.)

Un-Freeze

Un-freeze an object. (Can only be performed by a Team Coding Administrator.)

 

Team Coding and Version Control Support

Provider logon

The version control system (VCS) must be configured in Team Coding before you can log in. For more information, see Install Team Coding.

To log in to a VCS from Team Coding

  • Team Coding | Provider Logon.

 

Version Control Systems

Using Git

  1. Go to Team Coding | Provider Logon. The Git login window opens.
  2. Enter your repository information, Git user name and Git email, and click OK. The Source Control Select Project dialog opens.
  3. Select your Git Sub Directory from the list of modules.
  4. Open the source control VCS Browser. You can browse Git controlled objects, open files in the editor, check in, check out or add files to the local Git repository.

 

Related Topics

Provider logon

Version Control Systems

More about Git and SQL Navigator

Using Perforce

  1. Go to Team Coding | Select VCS Project.

    If loading workspaces automatically from the server, or a workspace is already in the local cached list, then select an existing workspace from the list.

  1. Enter your Perforce user name and password, and click OK.
  2. Select the Perforce project (depot) for use in SQL Navigator.

 

Version Control Systems

More about Perforce and SQL Navigator

관련 문서

The document was helpful.

평가 결과 선택

I easily found the information I needed.

평가 결과 선택