Improved Team Coding facilities

The new Team Coding module in this version of SQL Navigator represents a combination of the functionality previously provided by Team Programming and VCS in Version 3.2. It addresses various issues raised by existing users of the previous functionality, provides additional flexibility, and permits the possibility of future enhancements which were not possible in the previous implementation.

Here are some highlights. For details, you can browse the Version Control and Team Coding topics.

$image\Sqln0004.gif$ Team Programming (check-in and check-out) and version control features now operate in conjunction with each other.

$image\Sqln0004.gif$ The simple Schema Mapping model has been replaced by flexible Code Control Groups (CCGs) that help you control objects from one or more schemas, using customizable groupings.

$image\Sqln0004.gif$ You can organize objects into CCGs by using Object Masks representing both specific database objects and collections of similar objects (by using the Oracle % wildcard). You can also set up exclusion masks to exclude specific objects from a CCG.

$image\Sqln0004.gif$ Even without a third-party version control product, you can use CCGs, so that referenced objects will be tracked by Team Coding (though without revision history).

$image\Sqln0004.gif$ Scripts are now supported in Version Control.

$image\Sqln0004.gif$ All configuration data is now stored in the database under Team Coding control. Individual workstations do not need to be configured.

$image\Sqln0004.gif$ A more flexible security model is employed, making full use of Oracle security features.

$image\Sqln0004.gif$ Developers can remap their schemas to any CCG, removing the SQLNAV_ADMIN "super user" bottle neck.

$image\Sqln0004.gif$ The Version Control Browser now opens objects in a visual object editor, rather than in the SQL Editor.