Toad World® Forums

Team Coding with Subversion in Toad 11

I’m trying to find out a way to do the version control of our database objects using Toad. I’ve successfully configured subversion but now I have 2 problems:

  1. I’m not able to change the working directory / VCS Project to a subdirectory in my SVN-Path when I’m defining a Code Collection.

I want to store the database objects in the OBJECTS directory, which has the following path on the svn server:


In the Code Collection Window I can only specify as a VCS Project the Module Name. Nor is it possible to change the Working Directory.

I’ve found a solution for this (changing the VCS Project in the TC_GROUP Table on the Team Coding Installation Schema, turning the triggers on that table off / on before and after this so that the TC repository doesn’t get corrupt) but I’m not very happy with it.

  1. Is there a way for an TC Administrator (having the TC_ADMIN_ROLE) to set a schema as mirror schema? I just can do that if I grant the owner of the future mirror schema the TC_ADMIN Role and let him to that.



Hello Bogdan,

Each VCS Provider is handled slightly differently in Team Coding.

Modifying the TC_GROUPS by disabling Triggers won’t work. I strongly
suggest that you delete and re-add your code collections to correct this.

The current SVN configuration in Team Coding does not allow you to select a
different working directory for different object types. The only way to
accomplish this is to set up a Code Collection for each object type and map each
collection to a different SVN project. Each project is mapped to its own working
directory and Team Coding will save the source files for objects in these

You can’t set up mirroring for users as you describe. To Mirror to a
master schema, you must log in as the user who is not the owner of the Schema in
the Code Collection. I think the TC_ADMIN route you suggest sounds like it has
some potential, and suggest you add it to the Toad Idea Pond.

Please let me know if I can be of any additional assistance


Hallo Stephen,

thank you for your answers. I gues though that I wasn’t too specific in describing the first issue. What I’m missing there is the possibillity to map a code collection to a subdirectory in my svn repository.

At the moment it is only possible to map the main directories in a repository to a code collection.

Our SVN-Repository directory structure looks like this:





I can only map the MODULE1 and MODULE2 directories to a code collection (meaning all my objects will be saved there) but not subdirectories (like MODULE1\DB\OBJECTS).

As I said, by manually changing the VCS Project in the TC_GROUPS Table to a subdirectory solved my problem, but I don’t thing that’s the best idea to do that.

Regarding the 2nd issue, I will add it to the Toad Idea Pond. I think this will simplify the way the mirror schemas are beeing managed.

Kind regards,


I’m glad your fix worked J Let me test a similar configuration here and
see if we can enable a modification in the Code Collections edit window.