RE: Controlling changes to database - Team Coding

That's a good, easy suggestion - worthy maybe of the Toad FAQ web page :)

From: [email protected] [mailto:[email protected]] On Behalf Of Norman Dunbar
Sent: Wednesday, January 11, 2012 12:55 AM
To: [email protected]
Cc: Bryan, Timothy
Subject: Re: [toad] Controlling changes to database - Team Coding



On 10/01/12 16:12, Bryan, Timothy wrote:
> ...
> Today, a co-worker changed a package and
> compiled it without checking it out. He is not running the same version
> of TOAD as his is 10.1 and I am using 11 and he has not setup his local
> repository. It was done for the purpose of a test, but now we ask how to
> control changes. Does this get controlled, or is this a procedure task?
> We are logging in as the schema owner.

There's a Toad option that I use when I've got database scripts and
objects under Subversion version control -

View->Options
Editor/compile
Then uncheck "Allow compiling when source loaded from database".

This will prevent your developers from ever compiling any database
objects, unless they have loaded the script to make the required changes
from a file as opposed to generating the script from the Schema Browser,
for example, and then sending it to the editor.

Obviously, it's simple for anyone to turn off the option, but I find it
useful in conjunction with version control.

--
Cheers,
Norm. [TeamT]