Re: views on views on views

From: Lyndon Tiu <>
Date: Thu, 26 Mar 2009 17:36:20 -0500
Message-ID: <>

Jared Still wrote:
> Materialized views?
> Aggregations via analytic functions?
> ( In a view )
> PL/SQL for data intensive manipulation?
> (often much faster than external app layer - just return results)

Yes. These are great reasons.

But it depends how big your DB is and how much data is being retrieved by the application at a time.

Most databases are not that big and the application does not need the whole database to calculate some number. If that's the case, then we do not require all these DB features. Using these just makes more trouble that it is trying to solve.

The DB I am talking about is not big and the application does not retrieve the whole database to make some really complex calculation. So getting rid of those views on views on views ... and moving to the application was a justifiable step to reduce complexity and blood boiling. Some disagree, yes. But that's how it is and it seems to work.

Lyndon Tiu
Received on Thu Mar 26 2009 - 17:36:20 CDT

Original text of this message