| Subject | Re: Creating INDEXes on a VIEW |
|---|---|
| Author | Aage Johansen |
| Post date | 2003-07-31T21:29:06Z |
On Thu, 31 Jul 2003 19:26:30 +0000 (UTC), Brian L. Juergensmeyer wrote:
indexes for supporting ORDER BY isn't always efficient.
The optimizer may be better now, but I do remember when I had to write the
query so that no index were used for the ORDER BY - using the index was
significantly slower than having the engine sort it.
YMMV.
--
Aage J.
>> ...Indexes is best used for supporting the WHERE clause, of course. Using
>
> We would need to be able to use some form of indexing on the result set (be
> it an ORDER BY in the view definition or indexing the underlying tables) in
> order to retrieve data indexed in a certain way.
> Why would you not include an ORDER BY in a VIEW definition?
indexes for supporting ORDER BY isn't always efficient.
The optimizer may be better now, but I do remember when I had to write the
query so that no index were used for the ORDER BY - using the index was
significantly slower than having the engine sort it.
YMMV.
--
Aage J.