Team Coding and Version Control Support. Dell 7.2
تبلیغات
تبلیغات
7
Team Coding and Version Control
Support
Code Control Groups
How do CCGs work?
SQL Navigator’s code control groups (CCGs) are the most powerful and flexible feature of Team Coding.
Following are examples of how CCGs can be useful.
Example 1: A Single Application
Suppose you have a schema containing stored programs that all relate to a single application on your Oracle instance. You can easily create a CCG that includes all objects in that schema, and map it to a Version Control project in your provider’s repository.
Example 1 Using CCGs to map objects from multiple schemas to one VCP Project
SQL Navigator 7.2
User Guide
107
Excluding objects
If the schema also contains some objects that you do not want controlled (for example, you may have some test packages which don’t form part of your application), it is a simple matter to add an exclusion reference (Object
Mask) in your CCG. For more information, see Code Collection Viewer on page 110 .
Including certain object types and schemas
If your application contains some objects located in a different schema, it is easy to modify the CCG to include those objects. To take this a step further, you can also configure your CCG so that it contains any of the following: l object Masks based on a particular schema l stored programs of any type or a particular type (such as Trigger) l objects of any name or using a name mask (such as ACC_%).
Any object mask can used to exclude as well as include, so you can readily include a group of objects, but exclude (for instance) all objects of name like DBG_%
Scripts
If your application involves ancillary scripts, you can include references to these scripts in your CCG. As with other objects, you can use wildcard masks and exclusions.
SQL Navigator 7.2
User Guide
108
Example 2: Multiple Applications
If you subsequently start development of a second application, using objects stored in the same schema as the one used for the first application, you can then simply create a second CCG. This new CCG would contain object masks for the stored programs that are related to your new application, and you would associate the new CCG to a different project in your version control repository.
For example, if second application is made up of procedures whose names all begin with a common prefix such as "ACC", your second CCG would contain an Object mask for all procedures in the schema with a name like
ACC%. Team programming automatically recognizes objects with names matching the new object mask and maps them to the second VCP project rather than the first.
Example 2 Using CCGs to map objects from one schema to different VCP projects
Code Collections Viewer
Use Code Control Groups to organize your controlled objects into groups associated with development projects.
For example, you can create multiple Code Control Groups for a single Oracle instance, each group pointing to the stored programs relating to a particular customer application.
TIP:
Enable Code Control Groups from
|
SQL Navigator 7.2
User Guide
109
Toolbar
Icon Tool tip
Add Group
Description
Create a Code Control Group.
In the New Group dialog
l
Enter a descriptive name for the Group.
l
If you are using a third party version control product then select that product from the VCS Project list.
Open:
Open Group View or Modify the selected Code Control Group.
Open:
Delete Group Delete the selected Code Control Group.
Remap Group Change the descriptive name for the selected Code Control Group.
Change the third party version control product associated with the selected Code
Control Group.
Refresh Refresh the list of Code Control Groups.
Export to VCS Export objects to the third party version control product repository.
Open:
Import to
Database
Update your Oracle instance, or generate an import script, from the version control project for the selected Code Control Group.
TIP:
Use after you Map to group to update the objects in your schema.
Mirror to group
List all mapped users
Open:
Map the current user (the user logged on to the Oracle Instance) to the selected Code
Control Group.
Note: If the Code Control Group contains Object Masks for multiple schemas then you will be prompted to select the schema.
Open:
Linking a CCG to a user schema
Show the users mapped to the selected Code Control Group.
NOTE:
If the Code Control Group contains Object Masks for multiple schemas then show the selected schema.
Code Collection Viewer
SQL Navigator 7.2
User Guide
110
Define a Code Control Group: a set of database object masks and script masks identifying which objects are under Team Coding control.
TIP:
Enable Code Control Groups from
|
Toolbar
Icon Tool tip
Add DB
Object
Mask
Description
Specify an object or group of objects to be included in the Code Control Group.
Object masks are the symbolic references that define the Code Control Group. When
Team Coding processes a CCG, it associates a certain ranking with object masks in order to determine which database objects belong to that CCG.
In the Mask Properties dialog:
Option Description
Object
Type
Choose from View, Procedure, Function, Package, Package Body or All.
Schema Pick a user from the list, or type a schema name. You can use the % wildcard character.
Object
Name
You can type an object name, including the % wildcard. Alternatively, you can launch the
to choose an object matching the
Object Type and Schema settings.
Excluded Select to exclude any objects matching this object mask from the CCG.
Object mask ranking
Object masks are ranked based on the number of wildcards they contain. Highest ranking is given to the most specific mask, and when there are duplicate matching masks of different ranking the highest ranking mask takes precedence. Only when duplicate masks of the same ranking are encountered is it not possible to resolve the object to the CCG for which it belongs.
The mask rankings are, from highest to lowest:
Specific object reference:
Trigger SCHEMA.NAME
One wildcard only:
Any Type SCHEMA.NAME
Trigger SCHEMA%.NAME
Trigger SCHEMA.NAME%
Two wildcards:
Any Type SCHEMA%.NAME
SQL Navigator 7.2
User Guide
111
Icon Tool tip Description
Any Type SCHEMA.NAME%
Trigger SCHEMA%.NAME%
Three wildcards:
Any Type SCHEMA%.NAME%
Add Script
Mask
Specify a group of file server scripts (or a specific script) to include in the selected Code
Control Group.
In the Mask Properties Dialog:
Option Description
File
Name/Mask
Type a file name or mask using the * wild card, or browse to a file by clicking the ellipse (…) button.
Include
Path
File Path
If this option is selected, the mask will apply only to files in the directory specified under File Path. If this option is not selected, the mask will apply to files in the user’s working directory.
The directory to which this mask applies. Requires that Include Path (see above) be selected.
Exclude from the CCG any files matching this object mask.
Excluded
Delete
Mask
Edit Mask
Properties
Refresh
Mask
Delete the selected mask.
Edit the selected mask.
Refresh the list of masks.
TIP:
To create a code control group for all objects in the schema except procedures, you have to create two masks. The first one is to include all objects in that schema. The second one is to exclude the procedures. If only the second mask is created, it will not have any effect on the procedures at all.
Linking a CCG to a user schema
Team Coding allows developers to associate their own schemas with a Code Control Groups. When you open an object in your own schema, SQL Navigator searches for the object in the mapped CCG and opens it just as if as if you had opened the object from the original schema. If you check out the object, the archive for the original schema becomes Locked to other users, and the database object status is Locked for both schemas.
This is useful in cases where you often work in your own schema on projects containing objects that actually exist in another schema, or work on more than one project over a short period.
In essence, mapping a user to a CCG is equivalent to creating a new CCG identical to the mapped CCG, but with all Object masks pointing to a particular user schema. The same Version Control archive is shared between the user schema and the other (production or development) schema.
SQL Navigator 7.2
User Guide
112
TIP:
l
If the CCG contains Object Masks for multiple schemas, follow the prompts to select the schema you want.
l
Click Import to Database to update the objects in your schema.
Example -- Linking a CCG to a user schema
Can developers work on common code in their own schema? Yes—Team Coding accommodates this requirement through User Mapping.
For example, assume you have common schema(s) containing all the code for your development environment, but you would prefer that your developers check code in and out of your source control product using their own schema. Then at an appropriate time, you would update your "master" schema(s) for testing purposes before moving your code to Production.
User Mapping allows developers to work on their own copies of objects existing in a schema (the "master") that is controlled by a CCG (Code Control Group). This means that the objects in the master schema can remain unchanged during development, until the master schema is updated from the version control system using the
Import function. (Note: the CCG must be exported to the version control system before it can be imported into the master schema.
This example shows how a developer can map to the REPORTS schema, for which a CCG has been created. To add copies of the master schema’s objects to the developers’ schemas, each developer must import the CCG.
Mapping the developer Scott to a CCG called REPORTS
1. Log in as the developer SCOTT.
2. From the Team Coding menu, open the Code Control Groups window and select the REPORTS Group.
3. Click the Map to Group button, and verify that the user mapping icon appears beside the group name.
4. In the Code Control Groups window, click the Import to Database button.
5. In the Import into Database window, select the objects to import. Only those objects found in the VCS for this CCG are shown. When selection is complete, click OK.
6. In the Import Options window, select the Update another schema option, and click OK to begin the import.
Done! Scott can now check out the REPORTS objects from his own schema. When a user-mapped object is checked out or checked in, the Team Coding Check Out/In dialog will show the object’s Master Owner.
When a developer has a copy of a user-mapped object checked out, other developers are not allowed to check out their copies, and neither is the master owner.
Import Dialog
Import objects from your third party version control product.
SQL Navigator 7.2
User Guide
113
In the Import dialog
Select and exclude objects for import. The Import listing is populated based on existing archives contained in the third party version control product repository (objects do not have to exist on the Oracle instance), but filtered down to only those objects defined in the Code Control Group.
Select import options
The following options are available:
Description
Create or update objects in the original location in the Oracle instance, as per the Code
Control Group and archive file names.
Option
Update original schema
Update another schema
Add new revision to
VCS
Update database
Generate import script
Choose an alternate destination schema. All objects will be created in this schema regardless of the original object for which the archive was created.
You must have the appropriate privileges to create objects in the destination schema.
Create a new revision in the third party version control product repository for each archive, using the comment entered here to indicate the reason for the new revision
Update the objects in the selected schema.
Instead of updating the database, generate an import script and open it in the
TIP:
Save or print the status report as required.
Export Dialog
Once you have configured code control groups (CCGs), you can l
Construct a first revision of an application development project in your version control repository.
l
Create a new revision in your repository for all objects—for example, when you have completed your project and updated your production server.
TIP:
You should have access to all the objects referenced by the CCG. Otherwise, the process will need to be launched multiple times by all the different owners of the objects.
In the Export dialog
Select and exclude objects for export.
SQL Navigator 7.2
User Guide
114
Select Export options
The following options are available:
Option Description
Add objects not existing in the repository
Allows new stored programs to be added to the VCP repository. Any objects for which there are already VCP archives will not be updated
Create a new revision for existing objects
Forces all existing archives within the repository to be updated, as well as adding new archives for any new database objects
Create a revision only if the object has changed
Compares the object in the database with the archive in the repository, updating it only if it differs. This is useful when objects have been modified by a tool other than
SQL Navigator
Prompt individually for all existing objects
Comment
Permits the you to choose for each object that already exists in the repository whether or not it will be updated.
Lets you enter a comment to be applied to all new revisions created in the repository.
TIP:
Save or print the status report as required.
Team Coding Viewer
The Team Coding Viewer shows details of objects under Team Coding control, including which objects are currently checked out and when they were last checked in.
TIP:
Enable Team Coding and the objects under Team Coding control from
|
Toolbar
Icon Tool Tip
Refresh List
Filter
Description
Refresh the list of objects in the Team Coding Viewer.
Show only the object types that you are interested in.
Click to open the Team Group Filter window.
l
Select the schema object types you want to see.
l
Clear the schema object types you do not want to see.
SQL Navigator 7.2
User Guide
115
Icon Tool Tip
Get Latest Revision of Object
Check Out Object
Check In Object
Description
Get the latest version of an object or script as it is held in the Version Control repository.
The Get Latest Revision command overwrites the version of the object or script in the database, replacing it with the latest version held in the VCS repository.
You can use the
to compare versions before overwriting the object.
Check out or check in the selected object or script.
Open:
Undo Checkout Cancel the check-out. You are prompted to confirm that you want to discard any changes you have made and restore the database version of the item as it was prior to check-out.
Freeze Object
Un-Freeze Object
Open Object
Delete Record
View Differences between Object /
Script and latest
VCS revision
Confirm
Yes
You have made and saved changes to the object and you want to discard those changes.
Confirm
No
You have made and saved changes to the object and you want those changes to be retained in the database. As a result the version saved in the third party version control repository will be different from the version saved in the database.
Users with the LEADER role can freeze and unfreeze objects.
When you freeze an object other users are prevented from checking it in or out.
Open the selected object. May open the
Users with the LEADER role can delete objects.
Compare the selected database object with the latest VCS revision
Click Compare to VCS
Click SHIFT + Compare to VCS
Compare the selected object with the latest VCS revision
Compare the selected object with a VCS revision that you select
Requires that a version control product is in use and the selected database object is included in a Code Control Group.
View Object Details View team coding details of the selected object.
TIP:
You can make changes to a selection of multiple objects simultaneously.
List of Objects - Status Codes
In the List of Objects the Status column is of particular interest.
SQL Navigator 7.2
User Guide
116
Status
Checked Out
Locked
Frozen
Disabled
Meaning
Uncontrolled The object is not under Team Coding control
Available The object is available for check-out
The object is checked out to you
The object is checked out to another user
The object cannot be checked out or in by any user
The object is disabled due to a Team Coding specific error
Editable?
Actions allowed
editable None read only Check out
Freeze editable Undo checkout
Check in
Freeze read only Freeze read only Unfreeze read only None
Version Control Browser
Show version control archives. Show differences between revisions. Check out objects and scripts.
NOTE:
Refer to the SQL Navigator Release Notes for more information on Third Party Version Control products. This topic is not applicable to users of SCC API Team Coding support. Refer instead to the documentation for the third-party product in use.
Toolbar
Icon Tool Tip
Refresh
Description
Refresh the list.
Get Latest
Revision of
Object
Check Out
Object
Check In
Object
Undo
Checkout
Get the latest version of an object or script as it is held in the Version Control repository.
The Get Latest Revision command overwrites the version of the object or script in the database, replacing it with the latest version held in the VCS repository. You can use the
to compare versions before overwriting the object.
Check out or check in the selected object or script.
Open:
Cancel the check-out. You are prompted to confirm that you want to discard any changes you have made and restore the database version of the item as it was prior to check-out.
SQL Navigator 7.2
User Guide
117
Icon Tool Tip Description
Confirm
Yes
You have made and saved changes to the object and you want to discard those changes.
Confirm
No
You have made and saved changes to the object and you want those changes to be retained in the database. As a result the version saved in the third party version control repository will be different from the version saved in the database.
Open
Object
Open the selected object. May open the
.
View
Differences
Open the View Differences dialog. Select to: l
View differences between two specified revisions l
View differences between the selected revision and the database object (via
Code Control Groups) l
View differences between the selected revision and any database object or file system script
Click OK to open the
TC Locks option
On the Version Control Browser, there is an option of setting TC locks. The setting on this option determines how SQL Navigator decides the status of the files under version control.
This option can significantly increase the time it takes to expand a project node. However, this option can be particularly useful when using CVS as the Version Control Provider, since CVS does not support locking of files.
In this case, using Show TC Locks is the only way you can see what files Team Coding has locked under CVS.
Note: After selecting the Show TC Locks option, remember to refresh any project nodes which have already been expanded, as this does not happen automatically.
The state of the Show TC Locks option will be saved when the VCS Browser is closed.
TC Locks not selected
When this option is not selected, the VCS Browser determines which files are locked by querying the Version Control Provider; essentially it is just showing the status of each file as it would look in the provider's own GUI.
TC Locks selected
When Show TC Locks is selected, the VCS Browser will attempt to determine if a file is locked by
Team Coding, through its association with an object. In this case, the file's icon is changed to either a Team Coding checked out icon if the object is locked by the current user, or a Team
Coding locked icon, if the object is locked by another user. These icons are the same as those used in the Team Coding Viewer.
If the VCS Browser does not determine that a TC lock affects the file, it will still show the usual
Version Control Provider locks, using a different locked icon, where appropriate.
SQL Navigator 7.2
User Guide
118
Check In / Check Out Dialog
Option Description
Comments Enter comments about the modifications.
The comments entered at check-in time will be visible in the Team Coding Viewer. If a thirdparty version control system is in use, the comments are also logged against the new revision in the repository.
Applicable when multiple objects are selected.
Select to apply a single comment to multiple objects.
Apply to
All Items
Same
Comment for All
Force
Revision
When using a third-party version control system select this option so objects that are unchanged are updated in the database, so that new or changed comments can be stored.
On checkout: Follow the prompts to check the item out or choose Cancel to open it in read-only mode.
Different Files Dialog
When you open an object or script, Team Coding compares it with the latest revision in the VCP repository
(unless it is checked out). Team Coding advises when the database object or script differs from the version saved to the VCP repository.
Such differences might be due to a number of factors; for example: l
Another tool may have been used to edit the object l
A script may have been executed that modified the object l
The archive in the VCP repository may have been updated by another developer, or by some other means
You can choose one of the following options in the Different Files dialog.
Option Description
View Differences Open the
so that you can compare the two objects.
Open Database
Version
Load the database version into the VOE or Code Editor in Read Only mode.
Open VCS Version Update the database with the VCP repository version and load it into the VOE or Script
Editor in Read Only mode.
Make editable
NOTE:
Opening the version from the repository will cause the object in the database to be updated.
Check the selected item out for editing
SQL Navigator 7.2
User Guide
119
Team Coding Settings
Configure Team Coding for the current connection for all users. The options set here apply to all users.
NOTE:
Before enabling Team Coding:
Install Server Side Objects for Team Coding .
Configuration
Option
Enable Team
Coding
Use Code Control
Groups
Use 3rd Party
Version Control
Apply Team
Description
Select to enable Team Coding for the current connection for all users.
In the basic mode of operation, the following rules apply: l
Every supported object in every schema on the database must be checked out before being edited.
l
Supported objects are: l
Procedures l
Functions l
Packages and package bodies l
Triggers l
Views l
Object Types l
Object Type Bodies l
An object can be checked out to only one user at a time.
l
No Revision History is maintained.
NOTE:
The user enabling Team Coding should be granted the "Administrator" role.
A Code Control Group is a set of database object masks and script masks identifying which objects are under Team Coding control. Code Control Groups help you organize your controlled objects into groups associated with development projects.
NOTE:
When selected only objects referenced by a CCG are under Team Coding control.
Integrate with a third-party version control product.
When selected, individual CCGs can be related to a VCS project in the selected provider’s version control repository. This option also permits scripts residing on the file system to be managed by Team Coding. You can add references to scripts to CCGs.
When selected, objects not defined in a CCG can be controlled (but without revision
SQL Navigator 7.2
User Guide
120
Option
Coding to all
Objects
Version Control
Provider - Only
Show Installed
Providers
Description
history). All stored program objects will be under Team Coding control and must be checked out before they can be edited
When Use 3rd Party Version Control is selected, a list of all 3rd party Version Control
Providers is displayed. Select Version Control Provider - Only Show Installed
Providers to limit the list to providers installed on the current system.
NOTE:
When you select a provider on this list, selection does not in itself allow for maintenance of revision histories. The 3rd party version control product must also be installed on the current system.
File Extension Options
Specify the file name extensions to be used for database objects: Views, Procedures, Functions, Packages,
Package Bodies and Triggers.
These extensions are used to create the work files that are stored in the VCP project. Objects are stored in files named according to the following convention: SCHEMA.NAME.EXT
For example, the procedure MYPROC in schema DEV would be stored in a file in the VCP repository as
DEV.MYPROC.PRC
There is generally no need to modify these settings. Note that any change will also affect SQL Navigator
3.2 clients.
NOTE:
Do not change the file extensions after exporting objects to the VCP repository.
PVCS versions 5.2 through 6.0 will replace the last character of the file extension with ‘V’ when creating its internal archive. For this reason, it is important to ensure that: l
The first two characters of the file extension are unique (hence the default extensions for packages are not PKS and PKB) l
The character ‘V’ is not used as an extension (hence the default extension for views is not VEW)
General
Define how Team Coding should handle objects and scripts.
Default Settings for User Preferences
Option
Working
Directory
Description
Specifies a default workstation directory in which to store work files checked out from a version control product.
A local preference is also available to override this setting.
SQL Navigator 7.2
User Guide
121
Option Description
NOTE:
The version control product may override both these settings.
Automatic
Check Out
Select
Initiates a Check Out whenever the user opens the
or
for an object or script.
Open
Check In / Check Out Dialog . Follow the prompts to check the item in.
Clear Check out the object from the
Automatic
Check In
Force New
Revision on
Check-in
Select Initiates a Check-In whenever the user closes the
or
for a modified and checked-out object or script.
Open
Check In / Check Out Dialog . Follow the prompts to check the item out or
choose Cancel to open it in read-only mode.
Clear Check in the object from the
Allows a "comments-only" revision to be created in the repository. In other words, allows a new revision to be created in the VCP even if there has been no change to the object or script itself, but only to the comments.
NOTE:
The check-in dialog also provides this option; this setting simply sets the default behavior.
Global Settings
Option Description
Update database after Check-In
Use Trigger
Description for
DDL
Forces the database object to be updated after a check-in so that it is identical to the checked-in work file. This option is useful when the version control product performs keyword-expansion when files are checked in.
When using Team Coding with triggers, EXTRACT DDL is used to store the DDL of the object in the VCP repository. For triggers, though, there are two ways this text can be created.
l
Construct the DDL from the Data Dictionary. (default) l
Use the complete DDL from the description field in the Data Dictionary.
When selected, the Check-In dialog requires that the user enter a comment before the dialog can be closed.
Force comment during Check-In
Deny "Drop" for
Checked-
Out/Frozen
Objects
When selected, disallows the Drop action on objects that are checked out or frozen.
NOTE:
l
This will not prevent objects from being dropped by means of the Oracle
"drop" command executed by user DDL.
l
The
General | "Drop" and "Truncate" safety options
| No drop for Stored
Programs/Triggers preference takes priority over this preference.
SQL Navigator 7.2
User Guide
122
Script File Extensions
Specify the extensions that will appear in the "Files of type" drop-down list for Script Files when you add script masks to a CCG.
Use a semicolon as a separator; for example:
*.SQL; *.DDL
Team Coding Status Dialog
Show the privileges granted to the current user.
Show connection details, such as l which features are available l which version control product support DLLs are installed l which one is currently in use.
Click Settings to open
.
If system errors exist, click Errors to view error details.
Version Control Products
Concurrent Versions Systems (CVS)
You can use Concurrent Versions System (CVS) with SQL Navigator's Team Coding feature.
In addition, you must have a CVS client installed on your system (for example, WinCVS, CVSNT, TortoiseCVS).
Team Coding has been tested with: l
CVS clients 1.11.9 and 1.11.17 and CVSNT clients 2.0.8 and 2.0.41a with the pserver authentication method.
l
CVS client 1.11.12 with pserver and ssh.
l
CVSNT clients 2.0.11, 2.0.26, 2.0.34, and 2.0.41 with sserver, pserver, and sspi.
l
CVSNT client 2.0.14 with sserver, pserver, sspi, ssh, ext, and local.
CVS Configurations Options
On the CVS Configuration Options dialog box there are several options you can use to configure how SQL
Navigator works with CVS.
SQL Navigator 7.2
User Guide
123
CVS
Option Description
CVS
Executable
Enter the name of the CVS program file here. The default is CVS.EXE. If your file is different, you can enter it here.
You can specify the full path to the file, such as C:\Program Files\CVS\cvs.exe. This will force
SQL Navigator to use the specified program.
If you enter only the file name, rather than the entire path, the location of the program file must be in your system path. SQL Navigator will then use the first occurrence it finds of the specified file name.
Global
Options
Use this option to specify any global options 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.
The default is -f.
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
.
Dates and Times in CVS Output
Option Description
Date
Format/Separator,
Time
Format/Separator
These options tell SQL Navigator how CVS will send dates and times. This lets SQL
Navigator present correct revision date and time stamps in windows such as the VCS
Browser.
The default for Date Format is: yyyymmdd
The default for Date Separator is: /
The default for Time Format us: hhnnss
The default for Time Separator is: :
Available
Date/Time formats
Format
d dd m mm yy yyyy
Display
Day as a number without a leading zero (1-31)
Day as a number with a leading zero (01-31)
Month as a number without a leading zero (1-12)
Month as a number with a leading zero (01-12)
Year as a two-digit number (00-99)
Year as a four-digit number (0000-9999)
SQL Navigator 7.2
User Guide
124
Option
Time Zone
Login
Login
Automatically
Password Prompt
Timeout
Login Timeout
Time Between
Keypresses
Description
Format
s ss h hh n nn
Display
Hour without a leading zero (0-23)
Hour with a leading zero (00-23)
Minute without a leading zero (0-59)
Minute with a leading zero (00-59)
Second without a leading zero (0-59)
Second with a leading zero (00-59)
This option tells 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.
The default is 0000.
These options control SQL Navigator's behavior when attempting to log into CVS. SQL
Navigator creates a console window and executes the CVS Login command at the command prompt. When the password prompt appears, SQL Navigator sends the password you have specified.
When this option is checked, upon connecting to the database SQL Navigator logs in to
CVS without prompting you. The most recently used CVSRoot will be used.
To use this option, the following must be true:
l
The Team Coding option "Disable Login Prompt on Connection" is UNCHECKED l
The TC=NO command-line option is NOT used l
You have previously logged into CVS in SQL Navigator l
The previous login used an authentication method not requiring a password
OR: You checked the Save Password option on the login form
Enter the amount of time, in seconds, you want SQL Navigator to wait for the CVS password prompt. If the timeout expires before the password prompt appears, the login will fail.
The default is 10.
Enter the amount of time, in seconds, that you want SQL Navigator to wait for a login result to be returned after the password is sent. If the timeout expires before a result is returned, the login will fail.
The default is 10.
This option controls the amount of time (in milliseconds) 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.
SQL Navigator 7.2
User Guide
125
Option
Restore Defaults
Description
Click Restore Defaults to restore all options to their default values.
CVS Login Window
By default, when you have Team Coding with CVS set up, SQL Navigator will automatically display the CVS login prompt when you connect to the database.
NOTE:
l
If you do not want to connect automatically, then select Disable Login Prompt on Connection from View | Preferences |
l
When you log into CVS from within SQL Navigator, SQL Navigator opens a command prompt window to send the password to the CVS server. This window may open in the background instead of the foreground causing the login to fail. If this happens, select
|
Provider Logon and log in again.
To display the login prompt manually
Select
| Provider Logon
To login to CVS
Option
Select the root you want to use.
Description
Use
$CVSROOT
Environment variable
Specify
CVSROOT
SQL Navigator attempts to use your CVSROOT environment variable. When you select this option, your current CVSROOT environment variable is displayed in the first box.
NOTE:
This cannot be edited in SQL Navigator ; for instructions on changing environment variables, see you Windows Help.
Select this to specify which CVSROOT to use when issuing CVS commands. SQL
Navigator passes this to CVS using the -d option. Up to ten of the most recently used CVS ROOT values will be remembered. You can select from these by clicking the arrow in the right of the box.
Path Enter a path to your chosen working directory in the Working Directory box.
TIP:
Click Select to select a directory rather than entering the entire path by hand.
Password
Save
Password
Enter your password for the specified CVSROOT. If you have specified a CVSROOT that does not use password authentication (for example, the :local:method) you can leave this box blank. In this case, SQL Navigator will not issue a CVS login command.
If selected, SQL Navigator stores the password in an encrypted form in the CVS.INI file.
SQL Navigator 7.2
User Guide
126
Click OK to proceed with CVS login or Cancel to stop the login process.
NOTE:
Selecting Team Coding | Provider Logon will log you out of CVS for the current connection, even if you click Cancel at the logon prompt. To reconnect, click OK without changing any values.
Updating Working Folders
SQL Navigator requires that your working folders are up-to-date so that it can determine what files and folders are in your CVS repository.
You must update your working folders manually.
To update your working folders
Perform a full checkout and update with your CVS client. You can do this from the CVS command-line client by issuing the following CVS commands in your root working folder: cvs co .
cvs update .
Multiple Connections And CVS Logins
From one SQL Navigator instance, you can connect to multiple databases.
You can: l
Establish different CVS logins for each database l
Share the same login between several instances
After you have logged into CVS once, you will remain logged in, and SQL Navigator will not display the CVS Login dialog box as long as the first instance remains connected.
NOTE:
Each time a new connection to the database is established in SQL Navigator , the CVS login of the most recently established connection will be used.
To log into a different CVSROOT after initial logon, select Team Coding | Provider Logon. See
.
Authentication Methods and the CVS Root
Most CVS servers support several different authentication methods. The authentication method used to access a CVS server is specified in the first part of the CVSRoot. The CVSRoot contains the following sections
:authentication method:user@host:port:/path
All sections except path are optional. The following rules apply: l
A CVSRoot consisting only of a path will use the local authentication method. It is synonymous with:
:local:/path l
If the user section is omitted, the CVS client will use your Window login name.
l
The host section must be included for all methods other than local.
SQL Navigator 7.2
User Guide
127
l
The port section is only necessary when the CVS server is listening on a port other than the default port, which is 2401.
CVS Authentication Methods tested with SQL Navigator
SQL Navigator has been tested with the following CVS authentication methods: l pserver l sserver l ssh l sspi l ext l local
Using pserver and sserver methods
Using pserver and sserver is straight-forward.
l
Both require a username and password.
l
With both, SQL Navigator executes the CVS login command.
l
With sspi, username is optional. If a username is supplied, SQL Navigator executes the CVS login command. If no username is supplied, SQL Navigator will not execute the CVS login command.
Using local and ext methods
The local and ext methods do not require a password.
l
The local method is used to access a local CVS repository. This method is assumed if no authentication method is specified.
l
The ext method is used for SSH authentication. For more on using SSH, see
SSH Authentication Using The ext Method .
SSH Authentication Using The ext Method
SQL Navigator supports the use of SSH (Secure Shell) with the ext method as long as the following conditions are met: l
An external SSH client and SSH Authentication Agent must be installed and configured.
l
SSH authentication must be transparent. Toad cannot respond to requests for private key or passphrase.
l
The CVS_RSH user environment variable must be set to specify the SSH client program if the SSH client program is anything other than "ssh".
Example SSH configuration steps:
This configuration uses Plink as the SSH client and Pageant as the SSH authentication agent. Plink, Pageant and
PuttyGen are parts of the PuTTy software package by Simon Tathem.
This is just one sample configuration.
SQL Navigator 7.2
User Guide
128
1. Install PuTTy (including Plink and Pageant)
2. Generate public and private keys using PuttyGen.
3. Upload public key to the CVS server, which must be running SSHD.
4. Load Pageant and register your private key with it. Keep Pageant running whenever SSH is being used.
5. Set CVS_RSH environment variable to the path to plink.exe (for example: c:\program files\Putty\plink.exe).
6. Set CVSRoot to :ext:user@host:port:/path, where user = your SSH login name on the CVS server host = the CVS server hostname or IP address port = the CVS server port (optional) path = the path to the CVS repository on the server
(for example: :ext:[email protected]:2401:/usr/local/cvs/project).
SQL Navigator 7.2
User Guide
129
دانلود
پیوند عمومی به روز شد
پیوند عمومی به چت شما به روز شده است. You may view and manage your chat links after registration here.
پیوند عمومی سند
تبلیغات
