Version control of Oracle Stored Objects.

[Lig]

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

[DA Morgan]

IANAL_VISTA wrote:

DA Morgan <da******@x.was hington.edu> wrote in
news:1110065133 .857196@yasure:

The real BDFH builds a DDL trigger that raises an exception with all DDL
on the database and another that audits it. He/she then disables the
first trigger whenever making changes leaving the second one to create
the audit trail.

Alternatively, just nightly extract the current production code from the
repository and install it into the database. Any and all ad hoc, on the
fly or unapproved changes just get summarily overwritten.

And you do this with users connected? ;-)

--
Daniel A. Morgan
University of Washington
da******@x.wash ington.edu
(replace 'x' with 'u' to respond)

[Ed Prochak]

Who change the package on the server? If it wasn't you then someone is
not using source control.

You are missing a development process. Well, no actually, you have an
ADHOC development process. Having VSS or CVS, doesn't do you a bit of
good if developers don't use it. As others point out, until ALL your
developers agree to never edit code unless they have it checked out,
then you have merely the illusion of code control.
You have a choice: continue as a team of cowboy coders,
or change to work as a team of software engineers.

Good luck. You are going to need it.
Ed

[Galen Boyer]

On Fri, 04 Mar 2005, li*****@iol.ie 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?

Yes, give each developer his own schema and have him deploy the code
from source control to that schema. When he is done fixing his code, he
checks in. Then, only deploy code to QA, Staging, IDE's and Production
from Source Control.

--
Galen deForest Boyer

[glimmertwinfan]

Yes, give each developer his own schema and have him deploy the code
from source control to that schema. When he is done fixing his code, he checks in. Then, only deploy code to QA, Staging, IDE's and Production from Source Control.

--
Galen deForest Boyer

That's exactly how we do it and it works great.