Previous | Next
Topic: Another perspective on auto-compile
Conf: 550, Msg: 41907
From: Jason Dufair (firstname.lastname@example.org)
Date: 3/5/01 01:50 PM
Another perspective on auto-compile Jason Dufair jkdufair email@example.com
I'm interested in rolling out utPLSQL to my team for automating a lot of the tests we should have written years ago. Here's my problem - I'd like to use the auto-recompile option, but it requires that all of the source is on the same box as Oracle. All of our source is on an NT server (that is our version control server) separate from the Unix box that Oracle (7.3.4) is on. We don't really have the option of setting up NFS or Samba to make these machines talk to each other, either.
So what are my options? I was going to try to tinker with compile in utplsql.pkb, but I can't think of any way that the package could access my i: drive. I suppose I could write a SQL*Plus script to compile stuff (using @file.pkb...) and then call utPLSQL, but I'm hoping for something more elegant. Any ideas?
Does everyone else keep their source on the same box as their database server?