Controlling changes to database - Team Coding

Controlling changes to database - Team Coding

This process would keep the objects updated in the svn repository and once run in the database it would update there as well. The last question now then is the check-in / check-out within TOAD. If I just open the file in my local repository, with subversion it is marked as changed and needs update. I can use my svn client to just right click and do a SVN commit. How does the check-out in TOAD need to be used? Will it do the check-out only in subversion? If I use the schema browser and check a file out from the Team Coding menu, is it not checked out in subversion and updated in the local repository where then a subsequent Check-in would be needed?

Best Regards

Timothy Bryan
We are what we repeatedly do. Excellence, therefore, is not an act but a habit.
Aristotle

Timothy,

If you are using Team Coding in Toad as primary means of controlling your
objects, then Toad will handle the commits/check in etc in SVN. It will perform
a lock / check out on the Team Coding Database and also in SVN. When you do a
‘check in’ Team Coding does the reverse in the Database and in SVN.
There should be no need to commit manually with SVN in the normal course of
events. Of course there is nothing preventing your from doing this but that
would put SVN out of synch with the Team Coding database, not something I would
recommend J

Stephen

Morning all,

On 11/01/12 17:58, Stephen Beausang wrote:

There should be no need to commit manually with SVN
in the normal course of events. Of course there is nothing preventing
your from doing this but that would put SVN out of synch with the Team
Coding database, not something I would recommend J

You can, of course, check whether an SVN COMMIT will do anything at all
by running an SVN STATUS command in the local folder and checking for
any files flagged with 'M' for modified or '?' for not (yet) under
version control or 'A' for Added by not committed.

I should point out that I've never used the database version of Team
Coding with Toad, only what is known as Legacy Team Coding. I'm not
allowed to install any Toad objects into any of our development (or
Test/QA/Production) databases - my knowledge of that area of Toad is
non-existent I'm afraid.

Cheers,
Norm.

PS. svn status or svn commit also available via TortoiseSVN - if you
work in Windows and use Subversion, it's about the best tool there is.
If you use CVS, Mercurial or Git, then there's a Tortoise for you too!

--
Cheers,
Norm. [TeamT]