Re: Database Design Best Practice help
From: Sayan Sergeevich Malakshinov <malakshinovss_at_psbank.ru>
Date: Tue, 29 Jan 2013 13:38:46 +0400
Message-ID: <OFE92A38EC.3E716313-ON44257B02.00318B78-44257B02.003526D0_at_psbank.ru>
Toon Koppelaars wrote,on my timestamp of 28/01/2013 8:13 PM:
> Just create a union-all view on top of those hundred tables, and write a
> couple of instead-of triggers to deal with inserts/updates/deletes. Then
> have your "controller" based on top of this view.
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"
Date: Tue, 29 Jan 2013 13:38:46 +0400
Message-ID: <OFE92A38EC.3E716313-ON44257B02.00318B78-44257B02.003526D0_at_psbank.ru>
Toon Koppelaars wrote,on my timestamp of 28/01/2013 8:13 PM:
> Just create a union-all view on top of those hundred tables, and write a
> couple of instead-of triggers to deal with inserts/updates/deletes. Then
> have your "controller" based on top of this view.
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-lReceived on Tue Jan 29 2013 - 10:38:46 CET