[Xapian-devel] GSoC xapian node binding thoughts

Liam xapian at networkimprov.net
Tue May 29 06:23:12 BST 2012

On Mon, May 28, 2012 at 2:44 PM, Olly Betts <olly at survex.com> wrote:

> Generally, uint32 isn't necessarily the right type to use everywhere,
> and means things will go wrong if someone patches Xapian and rebuilds
> it to use (e.g. 64 bit document ids).

Javascript doesn't currently support int64. It goes up to 2^53. We should
probably raise an error if the Xapian build we're running against uses
int64 doc ids.

XOR can also take any number of subqueries.  And on trunk, OP_FILTER,
> OP_AND_NOT, and OP_AND_MAYBE can also take any number of subqueries
> (with OP(A, B, C) being interpreted as OP(OP(A, B), C)

XOR is missing from the online docs for Query(Query::op, Iterator,
Iterator, termcount)

We can include support for the other ops you mention and leave it commented
out for now.

Marius, that Query object is missing a parameter:uint32 member.

Also, it would be nice to support a mixture of strings and query objects
> as the subqueries (like we do in most of the dynamically typed languages).

You can include a term query in the list by writing {tname:'string'}, but
certainly we could let 'string' be a shorthand for that.

I'm dubious about wrapping the various iterators as methods which read
> all the entries from the iterator and return an array.

 We'll take optional start & count arguments for those guys.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xapian.org/pipermail/xapian-devel/attachments/20120528/c758aed0/attachment.htm>

More information about the Xapian-devel mailing list