Development vs. Test

Hello,

Due to disk space/horsepower limitations of our database server (Oracle 7.3.2), we have the following set-up: 1 schema (call it DEV) with objects released for testing/common development, with a set of public synonyms and permissions granted to all developers/testers. 1 login per user (call it USER), with ability to create their own objects -- for development purposes.

The problems we run into are:

1. Creating stored procedures/triggers under USER:
   • Cannot create a trigger on the table that is owned by DEV (understandable, but how can we do development?)
2. Referrential integrity: say, I want to test adding a column to a table. I make a copy of the table in USER, get some data, add a column. If the table I copied has some dependent tables, I will not be able to test adding to the table -- because dependent tables still reference the table from DEV, rather than from USER.

Creating a complete set of tables for each user, while possible, is not feasible due to the overhead of keeping it in synch with the main DEV environment.

What are the known WORKING solutions to the situation we're faced with? Thank you in advance.

Alex Vilner

-----------== Posted via Deja News, The Discussion Network ==---------- http://www.dejanews.com/ Search, Read, Discuss, or Start Your Own Received on Mon Mar 01 1999 - 09:00:48 CST