search for: classxapian_1_1writabledatabase

Hello, Two questions about using Xapian as a gdbm stand-in for an auxiliary database: - I am currently using single-term documents having the key as a single term, and the (small) associated data chunk stored in the document data record. Is this still the right way to do it? - There was an answer on the mailing list two years ago, saying that storing a few megabytes in the document

Hi, Is it possible to perform a search without flushing the index? I've got an application that updates the index every 4 hours but I need to be able to search the new data fairly quickly after the index is updated. The problem revolves around the fact that the update is often much less than 10 000 documents so it isn't being flushed until quite a bit latter. I realise I can do a flush

...rs until the changes were flushed. Opinions? While looking at this, I noticed the currently unimplemented transaction methods. The idea is to allow a group of operations to be specified as being applied as a unit. Either they all are applied, or none are. http://www.xapian.org/docs/apidoc/html/classXapian_1_1WritableDatabase.html#a7 This is actually very easy to implement like so: * begin_transaction flushes any pending changes and sets an "in_transaction" flag * if "in_transaction" is set, we ignore explicit flushes and don't autoflush * cancel_transaction closes and reopens the Btree tab...