Re: Controlling changes to database - Team Coding

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]


------------------------------------

Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/toad/

<*> Your email settings:
    Individual Email | Traditional

<*> To change settings online go to:
    http://groups.yahoo.com/group/toad/join
    (Yahoo! ID required)

<*> To change settings via email:
    [email protected] 
    [email protected]

<*> To unsubscribe from this group, send an email to:
    [email protected]

<*> Your use of Yahoo! Groups is subject to:
    http://docs.yahoo.com/info/terms/