[ewiki] Re: new db interface, virtual funcs, ::SEARCH()

> I think separate simple and complex searches are probably in order.  The
> current one being the simple to provide for searches such as we
> currently do and the complex one supporting the next search page.  The
> complex search should be able to search title and content as well as
> include and exclude words.

Actually I now choosed to have a simple/stupid multi-field-search wrapper
in the generic ewiki_db::SEARCH() interface than to carry this out into
each database backend.
However I see no reason not to allow backends to implement a ->MULTISEARCH
which then got called in favour if available.

But I'd also say, that the FutureSearch will certainly also come in a
sql/-only variant - after all searching is what SQL was made for!

Btw, look on http://opensearch.berlios.de/ - you can search our demo
site from there, and the actual sql-driven backend is already in our
plugins/lib/ directory, so we could use it today (without any XMLRPC
and server round trips) to implement a better search frontend. And as
it is an important feature, there may as well be a dozen frontends to
it.

mario

Other related posts: