>>What do you mean? You're going to create indexes on the fly? That's dirty and definitely not quick. SET KEY will knock your socks off!
>
>Not create indexes on the fly. The index list will be set on the fly based on the index. SET KEY I believe would workable. But, I'm not familiar with it, so it will take more time to implement.
You can easily create indexes on the fly, and still have reasonable performance, if you use a parameterized view to get the required data.
The index will only be created on the data you have fetched.
SET KEY doesn't give you this flexibility. Sure, you can create compound indexes, but you will require several of those, to cover all cases.
Difference in opinions hath cost many millions of lives: for instance, whether flesh be bread, or bread be flesh; whether whistling be a vice or a virtue; whether it be better to kiss a post, or throw it into the fire... (from Gulliver's Travels)
