I'm using this package repository on Ubuntu Edgy.
deb http://www.xapian.org/debian edgy main
and trying to get php4-xapian to work. There are lots of
missing functions.
If I install php4-xapian, and add the module to /etc/php4/cli/php.ini
and list the functions available (using get_defined_functions) with a
command line run of PHP both before and after, I find these ones are added
by presence of the module:
> xapian_version_string
> xapian_major_version
> xapian_minor_version
> xapian_revision
> auto_open
> auto_open_stub
> quartz_open
> inmemory_open
> muscat36_open_da
> muscat36_open_db
> remote_open
> remote_open_writable
I'm expecting things like new_database, but can't see them.
On the contrary, I /do/ find that function (and lots of other similar
ones) in php5-xapian, and it works fine.
What's going on with the PHP4 bindings again?
Francis
On Tue, Nov 14, 2006 at 11:23:09PM -0500, Francis Irving wrote:> I'm expecting things like new_database, but can't see them.You should now use "new XapianDatabase" instead of "new_database".> On the contrary, I /do/ find that function (and lots of other similar > ones) in php5-xapian, and it works fine.You should also now use "new XapianDatabase" for PHP5. Currently this is implemented as a PHP5 class whose methods call the flat function interface so the old functions are still there in this case. But they are essentially an implementation detail now.> What's going on with the PHP4 bindings again?This is where this was discussed last month: http://article.gmane.org/gmane.comp.search.xapian.general/3340 Hmm, I never wrote that script. Here it is now: http://www.oligarchy.co.uk/xapian/patches/xapian-php-update Cheers, Olly
On 11/22/06, Francis Irving <francis@flourish.org> wrote:> Oh yes, there's one interesting thing that using Xapian as the main > database has bought up. I'm making more extensive use of "metadata" > (i.e. prefixed keywords such as Da60pv94) using QueryParser. For some > meta-data would really like to have punctuation in keywords. e.g. > A/60/PV.57 instead of a60pv57. Sometimes the punctuation matters, and > I don't like the hack of replacing it with "x". > > Am I correct that keywords can only contain alphanumeric characters, > even if (for example) quoted? Is this something that has bothered > other people, or just me? >Yes, it has bothered other people too :-) For instance, the query "set_data" generates two terms. I wonder if the list of word-splitting characters could be made configurable in the QueryParser... Fabrice