>> To summarize: there are 6 sets of identical tables under a separate
schema and this requires 6 sets of procedures, functions, etc... They
want a better way to handle maintenance <<
- Code on set of packages with an if-then-else structure around each SQL
statement so that application accesses the proper tables. This requires
some duplicate code for SQL, but allows most of the actual application
logic to be shared.
- I do not like this idea as much, but you could combine identicial
tables for all 6 owners into one table adding an owner column to each
table. By having every SQL statement reference the proper owner you could
limit the data accessed in your test environment. In the actual
production environment this become a waste of space but a one or two byte
constant is not unreasonable. You could allow the customer to use this as
a plant or division indicator. Many systems have to have such a field for
functionality purposes. You may already have such a field.
Hope this is of help.
Mark Powell -- The only advise that counts is the advise that you follow
so follow your own advise
Received on Sat Jan 04 1997 - 00:00:00 CST
