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
The Team Coding Manager includes these tabs:
|
Note: If nothing is displayed on these tabs, it means that Team Coding was disabled by a Team Coding Administrator. |
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.
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.
To display revision history
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:
|
(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
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:
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.) |
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. 이용 약관 개인정보 보호정책 Cookie Preference Center