[Xapian-discuss] creating a database that's compatible with omega

[Sig Lange]

Great, that clear things up quite a bit. It really is quite unclear to
someone like me, You say values, so I natually think
xapian.Document.add_value(..), but infact I read it again and again
after it didn't work. I realized I needed .set_data(). I guess the
only way to clear this up in the docs is to perhaps say what functions
are used to set these attributes, or give examples of what *kind* of
data is stored in that particular space. What really got me was omega
seemed to do everything it could to fill in the gaps when displaying
the query results. setting .set_data() actually set sample=<...> where
as I never really set sample=<...>.  Some documents had titles but
most were untitled. Once I become more familiar with xapian i'll try
to bring together some helpful information.

Thanks everyone.


On Wed, 9 Mar 2005 23:06:03 +0000, Olly Betts <olly at survex.com> wrote:
> One thing I failed to mention - there's no point creating "U" prefixed
> terms in your own indexer "for compatibility".  They're only used by
> omindex for updating documents in an existing database, so if you aren't
> using omindex on a database, it doesn't need U terms.
> 
> Of course, your indexer may use these terms in a similar way itself, in
> which case it's certainly OK to add them (though a "Q" prefix is really
> a better choice for a general "uniqueid").
> 
> Cheers,
>     Olly
>