Re: pl/sql application build & release

From: Mark D Powell <>
Date: Thu, 3 May 2012 07:17:58 -0700 (PDT)
Message-ID: <7408374.326.1336054679164.JavaMail.geo-discussion-forums_at_yndr30>

On Tuesday, May 1, 2012 8:41:37 AM UTC-4, jeremy wrote:
> Hi just wondering if anyone could shed any light on good tools for
> managing the build and release of PL/SQL-based applications.
> We are using SVN and a mix of SQL*Developer & PL/SQL Developer & Textpad
> for code development.
> We manually build scripts for DDL changes for each release and manually
> build scripts to compile packages, triggers etc. and am wondering if
> there are any tools that any of you are using that assist in this.
> We use SVN branches/tags for each release but have to eb able to apply
> this release to multiple target databases.
> --
> jeremy

We also just use manual tools to make pl/sql and sqlplus script changes. For our official source for database objects we store after images of the code. That is each time a table is altered (column added, index added, etc) or a package is modified we generate a new code listing via home-grown dictionary extract (generate DDL) scripts and store the new source in sccs.

You can diff the most recent source file verse the previous version to determine the change made. Developers are required to provide the DDL to apply the change to system test and later production.

All object DDL that are dropped by Oracle when you drop a table are stored as part of the table source while independent objects such as functions, procedures, packages, and sequences have their own source members.

HTH -- Mark D Powell -- Received on Thu May 03 2012 - 09:17:58 CDT

Original text of this message