Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Usenet -> c.d.o.server -> Re: Version control of Oracle Stored Objects.

Re: Version control of Oracle Stored Objects.

From: Mark C. Stock <mcstockX_at_Xenquery>
Date: Sat, 5 Mar 2005 15:43:57 -0500
Message-ID: <v-6dnQztLIaNh7ffRVn-pA@comcast.com>

"Lig" <lignite_at_iol.ie> wrote in message news:ni%Vd.48814$Z14.36698_at_news.indigo.ie...
> 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

inspite of the best of policies, best management, and best intentions, it is not unusual to find one developer clobbering another -- especially in the heat of battle.

so, if telling your developers "the guys who post at c.d.o.* are going to think we're a bunch of unprofessional chimpanzees" isn't a good enough solution for you, try creating database triggers that prevent DDL operations unless the developer has 'registered' with the a custom source code control package.

this is even easier than pontificating about source code control policy, and does not even have to be bullet-proof -- just instrusive enough to serve as a reminder to the developer when he/she sees the "ORA-020000: Cannot compile object XYZ without initialing SCC Package". if you want it (nearly) bullet-proof, that's not too difficult to do, either, plus it can even be set up to be used as an audit trail of database changes.

refer to the 'CREATE TRIGGER xxx BEFORE ddl_event ON DATABASE' syntax, or contact me offline if you'd like more details.

(did anybody mention please don't to cross-post?)

++ mcs Received on Sat Mar 05 2005 - 14:43:57 CST

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US