Re: DDL Builds

On Thu, May 15, 2008 at 7:13 AM, David Mann <dmann99_at_gmail.com> wrote:

> At my previous job we had a formal change request process as Thomas
> mentioned. Originally we kept track of these changes manually but I ended up
> writing a Perl program that accepted a list of SQL scripts as input. The
> Perl program would run SQLPLUS for each SQL script in the list, then record
> the result in a table in the database. The success or failure was determined
> using SQLPLUS's WHENEVER SQLERROR EXIT command. Then the next time the Perl
> script was run it would query the 'changes' table and only apply new changes
> or reapply scripts that did not run successfully the first time.
>

Is more available?

Re the sql scripts passed as input: Are these 'ALTER TABLE' scripts? Do you query the data dictionary to determine if a change was already made?

Which leads to: How are you parsing the SQL of the input scripts?

SQL::Statement?

-- 
Jared Still
Certifiable Oracle DBA and Part Time Perl Evangelist

--
http://www.freelists.org/webpage/oracle-l