Re: Database Design Best Practice help

From: Fergal Taheny <ftaheny_at_gmail.com>
Date: Tue, 29 Jan 2013 11:45:04 +0000
Message-ID: <CAOuMUT4sBuf2rVukjuhCAQ=yEfS+23Hdngq-oYD9wHpW-cw1-A_at_mail.gmail.com>

Hi,
I think the suggestion is just to use the view for maintaining these lookup tables. In this way one screen in the app could be used to maintain all of them but all queries (lookups) would use the individual tables and not the view.

So you get the best of both worlds. Optimal lookups and an easy way to maintain them. Add a new lookup table; no problem just add it to the view and it can be maintained through the same maintenance screen.

Regards
Fergal

On 29 Jan 2013 09:39, "Sayan Sergeevich Malakshinov" wrote
> Unfortunately the views like that increases the chance to get inefficient
> plan, especially when client dynamically build queries with many joins of
> views with big number of tables, even if we increase
> "_optimizer_max_permutations"
>
> Best regards,
> Sayan Malakshinov
>
> --
> http://www.freelists.org/webpage/oracle-l
>
>

--
http://www.freelists.org/webpage/oracle-l

Received on Tue Jan 29 2013 - 12:45:04 CET