Performance of cascaded views ?

Hello everybody !

I'm a database programmer and I often have to use nearly equal queries to retrieve information from the database. So I thought about views. I could use a first view to select all articles from a catalog which are in the same group (for instance books) and a second view that will select all books from the first view that have a scientific theme.

So I always could use a view, that uses a view, that uses a view and so on instead of writing select-statements with more than 100 rows.

But what is with database performance? Is every view executed one by one and then the next one is executed on the result or does the optimizer make one big query from all of my views ?

So can I make extended use of views to make my database programming easier or will I get a really bad performance that way ??

Ciao and Thanks, Michael.

--
Michael.Keppler_at_bigfoot.com Received on Fri Aug 06 1999 - 08:25:00 CDT