Closed (fixed)
Project:
Xapian integration
Version:
6.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
4 Feb 2009 at 13:07 UTC
Updated:
20 Feb 2009 at 18:40 UTC
Jump to comment: Most recent file
Comments
Comment #1
jeremy commentedYes, this should be committed. Marking it as reviewed and to commit.
Comment #2
jeremy commentedPatch committed.
Comment #3
gerhard killesreiter commentedSorry, this patch was of course bogus. While it does not get the next node from the cache, it will not suppress the use of the cache at all. With this new patch I can index 10000 nodes on a setup where I was only able to index 200 previously.
Comment #4
jeremy commentedMy bad for not catching that. Indeed, the loaded node will be cached statically if there is no revision specified. So yes, the reset is the correct thing to do.
Comment #5
jeremy commentedCommitted to 6.x-1.x-dev. Thanks!
Comment #6
jeremy commentedAlso backported to 5.x-1.x-dev.