Re: "View" to a large schema

Karsten,

Thanks SO VERY MUCH for the assistance... not only for the idea but also for explaining it so clearly so that a non-Oracle person could get it. You've given me a very clear avenue of exploration and I appreciate it greatly!!!

-= Hypermommy =-

Karsten Farrell <kfarrell_at_belgariad.com> wrote in message news:<MPG.19748657318ea7f09897e6_at_news.la.sbcglobal.net>...

<<< snipped for brevity >>>

>
> Hmm ... I see your point. If you can't change the ASP without opening
> another can of worms (maintenance nightmares) and you can't change the
> schema (the ePortfolio application's Oracle userid that owns all the
> tables), then you don't have many options. Bad news.
>
> However, there might be one technique that will work for you. I can't
> guarantee it because I don't know how the ASP code retrieves the
> metadata (data about the tables). If you can (are allowed to) add a
> couple of Oracle userids, one for each doctor type -- for example, one
> named podiatrist, one named pediatrician, and so on -- then you could
> grant select on the tables used by each doctor type as follows:
>
> 1. connect to the schema userid that owns all the tables
> 2. grant select on <table_name> to podiatrist
> 3. repeat step 2 for each relevant podiatrist table
> 4. repeat steps 2 and 3 for each doctor type
>
> Then if the ASP selects from USER_TABLES (one of Oracle's views that
> returns all the tables accessible by a particular userid), you could
> setup an ODBC connection for each of your doctor types (eg, userid
> podiatrist). If, however, the ASP won't allow you to change the userid
> or it determines the tables used by some other method, then you're
> hosed. Or maybe someone else can come up with another idea.
Received on Thu Jul 10 2003 - 07:31:13 CDT