Rico Jansen <[EMAIL PROTECTED]> wrote: > The solution, as Michiel says, probably lies in the relm of full-text > search engines. Like Verity, Excalibur, Lucene (the last one is open > source btw). I know that Excalibur has a concept called overlap-iso > which maps all accented characters to their non-accented couter-part. > All searches take place on the non-accented indexes it creates in > that situation. I suspect a solution like that is better for the long > run. However it means quite a bit of work to solve, especially if there > is no support in the database for this stuff. However it was taken into > account in the query-project to support external indexes. I don't know > how much of that support has been fleshed out.
Actually, I would have implemented it already for postgresql (openFTS) and mysql (support is native I think), but I still don't really know how this functionality then should be called from e.g. taglib. I would expect a pseudo operator like 'FTS' or so, but it seams that it is needed to use LegacyConstraint. See also thread 'Database Search Query project conclusion' of december, but since then I had no time to actually explore this matter any further. It does not seem terribly complicated though, and I would propose to try to implement it genericly for 1.7.1 or 1.8.0 (but only for database which _do_ have some support for this, otherwise I would simply advice to choose another database). Michiel -- Michiel Meeuwissen Mediapark C101 Hilversum +31 (0)35 6772979 nl_NL eo_XX en_US mihxil' [] ()
