Better would mean something beyond full-text features that are built in mysql (MATCH AGAINST or LIKE). Perhaps an engine that also supports logical operators (in, or, without...), one-line searches etc.
As for Sphenix, real time indexing is a big issue and a drawback. But I think that it should be solvable. David Cramer's Curses Gaming has done it for sure ;) Simple example: I have a library of books and need to search items that match particular topics (or authors or keywords) in exact time scale. In my experience, full-text can do this task with a bit of wrapping inside django, but fails out with comparisons that are not exact (like typos etc). So, if you know for any django-search solution, please write it down. I'll be happy to check it out. Here is one that is full-text based, but doesn't have advanced indexing like Sphinx. http://www.mercurytide.co.uk/whitepapers/django-full-text-search/ On 24 dec., 09:46, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote: > On Sun, 2007-12-23 at 05:37 -0800, maco wrote: > > Yes, I've seen that, thanks anyway. > > > I've been googling for the past few days on this topic and I'm amazed > > that there is so little info about Sphenix on Django. > > Why are you amazed? It's not something that everybody is going to want > to do and the trade-offs involved don't necessarily make Sphinx the > obvious choice. > > Sphinx carries with it a number of restrictions that make integration > with Django a bit fiddly, particularly the universally unique identifier > requirements when querying across multiple tables -- that is contrary to > standard SQL design and very fiddly to enforce in Django, for example. > So it's not going to be everybody's cup of tea. > > > Is there any > > other way to implement advanced searching (better than Q search that > > is) that is better documented? > > What does "better" mean here? There are lots of ways to search over > database tables, but they all carry trade-offs. Either the API if more > complex, or there are constraints on the data (such as with Sphinx), or > they aren't as powerful (MySQL's native text search, for example). > > If a few web searches on likely words doesn't turn up anything, then > it's quite possible that nobody's done any really deep integration along > the lines you are after. Suggests that when you work out your solution, > there is a service to be performed in writing it up. > > In Open Source and volunteer work, sometimes you get lucky and > somebody's already done the work you need, sometimes you have to pick up > the hammer and nails and start building. > > Regards, > Malcolm > > -- > If at first you don't succeed, destroy all evidence that you > tried.http://www.pointy-stick.com/blog/ --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
