> Another thing I don't understand about what you have been saying, is the thing > about multiple tables. If you need a new table in the datastore for every new > keytype, then how can they be pluggable without changing the DataStore code? > And what does it give over just indexing them by type and value in a single > table?
The table doesn't need to go in the datastore. You can put it there, but then you have to upgrade your datastore for new key types. Now that I've give in to key handlers, I'd put the table in the key handler. The datastore can either store everything by CHK (assuming we make CHKs fundamental, which I think we should), thereby conveniently eliminating/merging duplicate files, or under a unique index (an integer). As far as the advantages of multiple tables, I suppose you could index it under a single table. It's important that the datastore doesn't have to know what the type means. One table per keytype would make for faster searches since items indexed under other keytypes wouldn't be looked at. I'm not really sure how you'd go about turning a two part key (keytype, key) into a single index key in a sensible way. _______________________________________________ Freenet-dev mailing list Freenet-dev at lists.sourceforge.net http://lists.sourceforge.net/mailman/listinfo/freenet-dev
