Thanks for the information, Mike :)
What use case(s) did you think of offhand for indexes pointing to other
indexes?
really only if the base table is an index. Then in that case if you
need an index on any other set of keys that is not the primary key of
the base table you would need an index on an index.
The biggest win for such a thing is that often applications only need
a single index and making them create a base table and index is just
unnecessary overhead in both processing and storage.
I have very limited experience with IOTs, but from what I've seen they
should only be used when you know they'll make a difference. As such I'm
not sure how much it would be used if it was ever implemented in Derby,
but it's cool to hear it was "thought of" in such a way that
implementing it isn't unfeasible!
Regards,
