XPost: comp.databases.oracle.tools, comp.databases.oracle.misc,    
   omp.databases.oracle.server   
   From: fvanbortel@netscape.net   
      
   Frank van Bortel wrote:   
   > Lig wrote:   
   >   
   >> We have an implementation of Oracle 9i database. We have a team of 20   
   >> developers working on a project. We use PL/SQL DEVELOPER and Visual   
   >> Source Safe to cotrol the source.   
   >>   
   >> The problem we have at the moment is one of version control.For the   
   >> moment, 2 developers can edit and compile a package.Because the   
   >> package is compiled on the DB Server,It is possible that a source   
   >> being edited by a developer could be overwritten by another.There is   
   >> nothing in PL/SQL that forces a user to check out and edit. We have   
   >> Visual Source safe fully integrated into PL/SQL Developer.But that's   
   >> only as much as it gets.VSS is not ORacle aware.   
   >>   
   >>   
   >> Are  there any products out there that can be used for Version   
   >> controlling Oracle Stored Objects that are Oracle Aware?   
   >>   
   >> Is there a better way of doing this?   
   >>   
   >> TIA   
   >> Lig   
   >>   
   >> Pl reply to   
   >> lignite     AT iol DOT ie   
   >   
   >   
   > install the CVS interface in PL/SQL Developer:   
   > http://www.allroundautomations.nl/plsvcs.html   
   >   
      
   Just realize you (probably) have that (fully integrated...)   
      
   There will always be ways to go around it - you can still   
   use SQL*Plus, or whatever to make changes.   
      
   The only way is to let your developers know you are serious   
   about source safe. Threaten to fire them if not used, surprise   
   them with a clean database on a Monday morning, whatever it takes.   
   --   
   Regards,   
   Frank van Bortel   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)