[Xapian-discuss] Rqt for Features

[Samuel Liddicott]

Eric B.Ridge wrote:

> On Aug 11, 2004, at 4:49 PM, Olly Betts wrote:
>
>> On Mon, Aug 09, 2004 at 12:16:59PM +0100, Olly Betts wrote:
>>
>>> On Fri, Jul 09, 2004 at 03:59:16PM +0100, Tim Brody wrote:
>>>
>>>> The cleanest method from outside of the API would be if 
>>>> replace_document
>>>> accepted a non-existent (to xapian) docid, in which case it adds the
>>>> document rather than excepting (i.e. SQL's "REPLACE" behaviour).
>>>
>>>
>>> This is something I'd noticed might be useful.
>>
>>
>> OK, this is now implemented in CVS.  Currently untested - I'll add some
>> test cases for this shortly.  If you test it, let me know how it goes.
>
>
> This is waay cool!  Using Xapian to index database records... now I'll 
> be able to kill my SQL lookup table of primary key<-->xapian doc id, 
> and just use my database primary keys as xapian document ids.  woo hoo!
>
When maintaining xapian databases this is correct.
Be aware that If you perform a search over multiple DB's that the id's 
will get munged into new id's in order to be unique over the result set.
There is (when I last heard) no simple way to convert from such munged 
id's back to the real id and real index.  This is only an issue if you 
will be searching over combined db's.

Sam

>