Re: Views and Indexes

> This means that it has to find its own indexes.
> So can you write an index over a View?

No you can't.

The whole point of SQL is to allow the database engine to do the heavy
lifting.  By separating the 'what order is this stuff in?' from 'what
columns are you interested in?' you give the database engine more
options to decide how to go get the rows for you.

This is very much related to the fact that using SQL is absolutely not
a replacement for native I/O in traditional OLTP type applications
with a traditional sort-of-normalised database.  It's like trying to
translate poetry (hand-crafted RPG) from one language to another word
by word and thinking that the results will still be poetic.

In order to make SQL perform as nicely as RPG, you need to start at
the beginning, just like we did with RPG.  Start with the database
design and proceed from there.  I know, I know - who has the time to
do that?  Probably none on this list.  So what's the point?

I think the point is that there are niche things that SQL makes so
easy where native is so hard, like dynamic searches and the like.
That's where I use SQL anyway.
  --buck