On Thu, Mar 26, 2009 at 3:36 PM, Lyndon Tiu <ltiu@xxxxxxxxxxxxx> wrote: > 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. > Everything can be abused. An educated and reasonable use of views, and of any other feature, makes for robust and scalable applications. Jared