Hi,

> Index in a multi-generational database seems like "Pandora's vase"...
> I don't know if optimizing a particular situation ( are there other tests
> under different CPU, OS ?) will break the "worst case scenario", giving a
> boost in some situation and kill performance in other..., I think "If it
> works well, don't touch it".

Te current-index structure wouldn't be touched and will stay as it is,
because it is a flexible as Jim explains (and it wasn't my idea to drop the
current index-structure).
The question is, is it intresting to add a new index-structure which could
be used when a user want it. I think it isn't bad to have 2 index-structures
inside a engine, but let's wait for some more comments/ideas.


Regards,
Arno Brinkman
ABVisie

-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Firebird links :
http://www.firebirdsql.com
http://www.firebirdsql.info
http://www.fingerbird.de/
http://www.comunidade-firebird.org/


Nederlandse firebird nieuwsgroep :
news://80.126.130.81