Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
Message from discussion pl/sql application build & release
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Mark D Powell  
View profile  
 More options May 3 2012, 10:17 am
Newsgroups: comp.databases.oracle.server
From: Mark D Powell <Mark.Powe...@hp.com>
Date: Thu, 3 May 2012 07:17:58 -0700 (PDT)
Local: Thurs, May 3 2012 10:17 am
Subject: Re: pl/sql application build & release

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 --


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.