Re: How to manage pl/sql source code

On Sat, 27 Apr 2002, post_at_new.message wrote:

> I want to use pl/sql on a project where all developers are working in
> their own schemas and use configuration control to share code. I want
> them to be able to refresh their schemas from configuration control
> whenever they like. As we are using extreme programming I expect this
> refresh cycle to occur at least daily for each developer.

We are using ant for this. All the database code, I mean all of it, is in source code control. Perforce is the source code management system and it is pretty slick. The developer syncs to the latest and then executes the particular database target passing the username/password_at_instance string for the sqlplus executable getting called. These targets are called by both the java developers that need a database schema built or the database developer who is working on the database code.

The only thing I find abhorrent is that these folks don't generate the code to submit to Perforce by an ER tool. They start the design in Erwin, but then actually make changes to the database code in the actual code. I would want to enforce a process that starts everything by using Erwin for the database maintenance.

-- 
Galen deForest Boyer
Sweet dreams and flying machines in pieces on the ground.