According to Sunny Fortune: > I have two questions on merging. > 1. Are the database files (db.docs.index and > db.words.db), that would have been created by a > previous merge, used for the next merge. Or does > htmerge create new database files using the files > created after the dig?
A little of both. htmerge uses the db.docdb and db.wordlist files, and recreates db.docs.index and db.words.db from scratch each time. That's the case for 3.1.x. In the 3.2 betas, all the database files are reused. > 2. For merging multiple databases, are all the dig > database files from all the sites used during the > merge. For example, if we have Site1 and Site2 having > their own db.docdb and db.wordlist files, during a > merge of Site2 into Site1, will both these files be > used to create the merged word database. Or is it > completely dependent on Site2's dig files and Site1's > word database file (db.words.db)? "htmerge -c Site1.conf -m Site2.conf" will merge Site2's db.docdb into Site1's, bumping up the DocIDs for Site2 appropriately, then it will merge the db.wordlist files similarly, and finally recreate the db.docs.index and db.words.db files for Site1 from the merged db.docdb and db.wordlist. The earlier db.words.db files, from before the merge, aren't used. However, it's important to run htmerge separately after running htdig on each of Site1 and Site2, before running htmerge -m, so that the wordlists are cleaned up before being merged. This is usually done anyway, if each of the Site1 and Site2 databases are created using rundig or some other script that does the htmerge after htdig. -- Gilles R. Detillieux E-mail: <[EMAIL PROTECTED]> Spinal Cord Research Centre WWW: http://www.scrc.umanitoba.ca/~grdetil Dept. Physiology, U. of Manitoba Phone: (204)789-3766 Winnipeg, MB R3E 3J7 (Canada) Fax: (204)789-3930 _______________________________________________ htdig-general mailing list <[EMAIL PROTECTED]> To unsubscribe, send a message to <[EMAIL PROTECTED]> with a subject of unsubscribe FAQ: http://htdig.sourceforge.net/FAQ.html
