Xapian discuss - Apr 2009 - Expanding the search in PHP

I tried using the simpleexpand.php from 
http://xapian.org/docs/bindings/php/examples/simpleexpand.php5

I get different results between PHP and the Omega expand (see below), 
I'd like to have the same functionality in PHP.
Could anyone suggest how to do it? Is there an example I could use?

Thanks,

Frank


And got the following results from PHP:

Zdefin: weight = 46.963883268652 
Zconfigur: weight = 46.52946510122   
configuration: weight = 46.299779195718
Zmodel: weight = 44.017152945486
Ztransit: weight = 43.896536471409
iso: weight = 43.372156818052
Ziso: weight = 43.372156818052
defined: weight = 43.324881918038
service: weight = 42.731413054732
design: weight = 42.727915046358
services: weight = 42.253200604566
Zincid: weight = 42.18125219367
provider: weight = 42.018278025832
Zservic: weight = 41.954492823328
Zuser: weight = 41.082687710465
activity: weight = 40.825484250849


But if I use omega I get:

configuration
iso
defined
service
design
provider
activity
incidents
security
control
model
impact
customers
performance
used
transition

Frank J Bruzzaniti a ?crit :
> I tried using the simpleexpand.php from 
> http://xapian.org/docs/bindings/php/examples/simpleexpand.php5
>
> I get different results between PHP and the Omega expand (see below), 
> I'd like to have the same functionality in PHP.
> Could anyone suggest how to do it? Is there an example I could use?
>   
Omega uses a custom ExpandDecider which rejects some terms during the 
expansion (terms with prefixes and stems among other things).
See end of file 
http://trac.xapian.org/browser/trunk/xapian-applications/omega/query.cc

Currently, you can't write such an ExpandDecider with the PHP bindings 
(IIRC, this is because Swig/php is missing a feature named "directors"
which allows to pass a php class to xapian).

As a poor workaround, you can change simpleexpand.php5 and ask for more 
terms (e.g. $eset = $enquire->get_eset(50, $rset);) and then filter the 
list or terms to display only those you want.

This is, of course, less efficient and you won't be able to guarantee 
how many terms the final list will have.

A better option would be to have a C++ utility class in the php bindings 
(e.g. SimpleExpandDecider) which would ignore terms starting with given 
prefixes (similar to SimpleStopper)... Badly, I'm not a C coder and I 
miss time...

Just my two cents...

Best regards,

Daniel