What about a mixed architecture: Filer in an SQL database, and btree indexes?
Seems to me like this (provided a index rebuild utility is available or
created) would take advantage of the database's robustness with minimal
effort. Any thoughts?
This is certainly possible, and if Xindice were the only client updating the database, the indexes would remain up to date as well (without manual rebuilds). It'd be nice to have a way to schedule rebuilds of BTree indexes for situations where the underlying relational database may change outside of Xindice's control.
-- Tom Bradford - http://www.tbradford.org Developer - Apache Xindice (Native XML Database) Creator - Project Labrador (XML Object Broker)
