Re: Version control of Oracle Stored Objects.

"Frank van Bortel" <fvanbortel_at_netscape.net> wrote in message news:d0ch1o$8if$1_at_news5.zwoll1.ov.home.nl...
> Noons wrote:
>> fitzjarrell_at_cox.net apparently said,on my timestamp of 5/03/2005 3:01 PM:
>>
>> <large x-posting deleted>
>>
>>>
>>> It has been my understanding that Visual Source Safe should disallow
>>> more than one copy of a file to be checked out, local copy or not.
>>> That being the case how on earth do you end up with two or more
>>> editable copies of a file?
>>
>>
>> If the developer gets a package off the database, quickly edits/compiles
>> and then starts working on something else off a file, it is quite easy.
>>
>>> I'd investigate why this occurs and put a stop to it at once, by
>>> ensuring all developers use VSS as it's intended. Several good
>>> suggestions to ensure compliance have been given you; use any or all of
>>> them to help fix this mess.
>>
>>
>> It's hard. PLSQL Developer gets the code from either the database
>> or a file. So there is really no control and it is easy for a
>> developer to do the wrong thing, intentional or not. Same happens with
>> Toad.
>
> One thing in favor of TOAD: it does have Team Coding, which has use some
> locking mechanism *in the database*, alongside VCC.
>
> It does not allow changes in objects, loaded from the database,
> when someone has these opened.
> All subsequent opens will result in read-only copies being loaded.
>
> Other than that, I'd rather use PL/SQL developer; it has far more
> sophisticated debugging capabilities, support for newer versions
> is better and faster, and the price... even a one user license of
> TOAD would be more than an unlimited license of PL/SQL Developer!
>
> --
> Regards,
> Frank van Bortel

AFAIR, the team coding 'locking' only works within TOAD -- so it is easily bypassed via SQL*Plus, etc.

Only way to tie source control to the database is with database triggers.

++ mcs Received on Sat Mar 05 2005 - 19:29:51 CST