Toad World® Forums

Access objects from VCS using Team Coding


Jan 10, 2017 1:58:00 PM by John Pocknell

This is a companion discussion topic for the original entry at


Hi, Thanks for the insightful post.
We are setting up git repository and intend to leverage Team coding for Oracle DB objects development work while having a version control in place.

As I understand, we need to first create a project under Team coding and then select all objects that we want to be enabled for version control or in other words all the objects being used in our client project.

There are hundreds of objects used in our project, so we need to select all of them for 2 reasons:
a. this will export DB objects as files in the local git repository path setting up the local repository. These files needs to be pushed to remote git repository so that initial repository set up is completed.
b. Going forward, for any development activities on DB objects since all the objects are enabled as team coding objects (TCX tables) all the developers can work directly under same project created initially from the Team Coding Manager without accessing the actual objects in DB.

a. To work with Team coding and for the initial git repository setup, is this the right way of doing it. i.e. Option 1: selecting all relevant objects when setting up Team coding projects so that file gets exported in local repository. If not, what could be the alternative way? Option 2: maybe, to export files outside of team coding manager to setup git repository and then create team coding project for each development cycle wherein we just mark only those objects that indeed needs to be modified?
b. Will Option 1 cause any performance issue using Team Coding?
c. When should we create projects in Team Coding? for option 1, I will have just one project, can all developers work on the same project? for option 2, is there any drawback of having n number of projects. what is the right way to use Team coding?

Any insight will be much appreciated. Thanks!