> From: Gilles Detillieux <[EMAIL PROTECTED]> > To: [EMAIL PROTECTED] > But, DocHead doesn't seem to be accessed anywhere > in code that isn't already accessing docdb, which makes sense, as it's > currently a field in docdb records. So, it seems to me that if you > handle the new dochead db in much the same way as the existing docdb, > that shouldn't introduce too much overhead or complications. Currently, > docdb is opened once in each of the programs, so why not open dochead db > at the same time, and leave it open until processing is done? Maybe even > write it as a sub-class of DocumentDB? If the DocHead database is moved into DocumentDB as a sub-database, then the opening and read/write problems could probably be solved much the same way I changed the handling of db.docs.index for the index-on-DocID change. Or maybe I missed something preventing that. brgds, H-P ------------------------------------ To unsubscribe from the htdig3-dev mailing list, send a message to [EMAIL PROTECTED] containing the single word "unsubscribe" in the SUBJECT of the message.
