<div class="gmail_quote">On Tue, May 29, 2012 at 7:24 PM, Olly Betts <span dir="ltr"><<a href="mailto:olly@survex.com" target="_blank">olly@survex.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
If you change sizeof(Xapian::docid) (and/or the sizes of other types)<br>
then that's an ABI change, so something built against xapian-core built<br>
with one docid size simply won't work with xapian-core built with a<br>
different docid size.<br></blockquote><div><br>So what happens when our lib tries to load or invoke the incompatible Xapian? Is it possible to prevent a crash?<br></div><blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
</blockquote><div class="im"><br></div><blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div class="im">
> In what context are int64 doc ids necessary? What % of installations use<br>
> them?<br>
<br>
</div>I doubt may people use them currently, quite possibly nobody does. But<br>
that's likely to change in the foreseeable future. We're probably near<br>
the point where you could conceivably build an index with this many<br>
documents on commodity hardware.<br></blockquote><div><br>We can support more than 2^32 values by converting to double (JS type Number) for 2^53. But beyond that the values stop converting correctly, meaning we'd throw an overflow and the user would have to hack the binding himself.<br>
<br>Marius can you make a note to treat docid as a Number instead of uint32, and check the values from Xapian for overflow?<br></div><blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
</blockquote><div class="im"><br></div><blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div class="im">
> Seriously, lazy-loading is oversold from what I've seen. If you have data<br>
> from real-world Xapian sites that shows a material advantage for it, I'd<br>
> love to read...<br>
<br>
</div>Any site searching a large Xapian database is relying heavily on lazy<br>
loading.<br></blockquote><div><br>For an array, it's necessary, so we'll take start & count args when building arrays. For objects, I question the value of lazy loading, save for very large fields.<br><br></div>
</div>