search for: chert_version

...up means that any indexes created prior to this revision cannot be read. Is this purely a cautious move to prevent errors, and, barring any obvious index format changes, can I safely force the current revision to read existing indexes? eg, by commenting out the throw in xapian-core/backends/chert/chert_version.cc. Or is there a better way? Thanks Henry

...g.o backends/chert/.libs/chert_spellingwordslist.o backends/chert/.libs/chert_synonym.o backends/chert/.libs/chert_table.o backends/chert/.libs/chert_termlist.o backends/chert/.libs/chert_termlisttable.o backends/chert/.libs/chert_valuelist.o backends/chert/.libs/chert_values.o backends/chert/.libs/chert_version.o backends/glass/.libs/glass_alldocspostlist.o backends/glass/.libs/glass_alltermslist.o backends/glass/.libs/glass_changes.o backends/glass/.libs/glass_check.o backends/glass/.libs/glass_compact.o backends/glass/.libs/glass_cursor.o backends/glass/.libs/glass_database.o backends/glass/.libs/glass_...