Martin T. wrote:
> Hi there.
>
> We use Toad for writing PL/SQL on our Oracle DB.
> Toad's SCC API allows for integration with source code control SW.
> The problem we see is that to work with source control, every time a
> developer works on a procedure, the procedure has to be saved as a
> local file to be versioned via SCC.
> Since a developer can edit/compile a procedure via Toad without saving
> locally, this will sooner or later result in someone doing changes
> without checking them in into source control.
>
> So, any ideas ?
>
> Better tools that also suport SCC API?
>
> thanks!
> best regards,
> Martin
>
At our location, we have two solutions in use:
- Toad integrates with PVCS. Use PVCS as your versioning system.
- Use the database as the source. Each night, we do an extract of
the database source code and compares it to a source code version
stored on the file system. (We use Java and compares a hash-value
of the source code String-object to the hash-value of the file based
copy). If the versions does not match - the database version is stored
in the file system and committed to CVS.
Received on Tue Jun 14 2005 - 13:29:51 CDT
