Re: Many Schemas

On 8 May 2001 08:40:07 -0500, Galen Boyer <galenboyer_at_yahoo.com> wrote:

>On Tue, 08 May 2001,
>SPAMBLOCK.Maxwell_Smart_at_ThePentagon.com.SPAMBLOCK wrote:
>> Well, imagining that each schema will need many views, that
>> weould be one view per table, and these views will need to be
>> joined together, would that be able to be tuned?
>
>I assume your application would be able to decide what user it
>needs to log into. Then, after figuring that out, the rest of
>the application accesses objects not caring about what schema it
>is currently accessing. These objects are views, but each schema
>owns the same named objects with exactly the same structures but
>just different data.
>
>Then, it would probably be easiest to write each view as a join
>of the underlying tables, instead of trying to make a set of
>views that then need to be joined together as another set of
>views to build the actual result sets you need.
>
>A scripting mechanism for replacing the company code would then
>allow you to write the views once and create them across all
>schemas.
>
>Does this help?

I am just ooking at the options. All information helps.

Part of the idea would be to make each schema separate, so that new queries can be created without having to worry about the effect on other schemas. Generally, this is done by adding a where clause on the main table.

If all the views were made only as needed, that might comlicate things. Though I do admit it is an interesting idea, assuming a script makes it for all schmas as needed.

Thank you for the information.

Brian Received on Tue May 08 2001 - 15:08:14 CDT