[KinoSearch] more abstract interfaces to kinosearch

[Marvin Humphrey]

On Jun 20, 2007, at 8:09 PM, Hans Dieter Pearcey wrote:

> * easier adding/loading: $index->add(@objects), or perhaps $index- 
> >load()
>   (using a predefined, per-schema data source)

I'm can see those statements meaning several different things.  Can  
you please elaborate on what it is you're trying to do?

> * easier searching, without using QueryParser, like SQL::Abstract  
> (since
>   that's what I'm used to):
>   $hits = $index->search({ foo => 1, bar => [ (qw(baz quux) ] })

Sounds like a good idea for an extension.  Constructing large queries  
via the KinoSearch::Search::Query subclass constructors can be  
tedious.  At the same time, I wouldn't want to have to implement/ 
document those constructs in Searcher itself.

> I've created prototypes of both of these for a project I'm working  
> on.  If
> anyone's interested, I'd love suggestions; I'll probably try to  
> spin them off
> into e.g. KSx::Manager or KSx::AbstractSearch.

I might encourage you to put those into KSx::Index::Manager and  
KSx::Search::Abstract, but it's just a suggestion.

Marvin Humphrey
Rectangular Research
http://www.rectangular.com/