We determined that Postgres was portable enough to any platform we'd host on, and went with TSearch2 and have been pretty happy. Having done hard-core search work in a previous life (www.singingfish.com), I know it isn't everything you can get in the search world, but it was sufficient for our needs. I personally feel that TSearch2 falls very nicely between better than the simplistic "like"+wildcard SQL statements and a sophisticated indexing engine like Lucene.
If you're willing to go "search server", you might even consider SOLR (lucene based search server with a web api). Especially if you scale out your front end's (the django app servers) horizontally in a large environment, it becomes appealing. How many front-end's you have actually becomes something to seriously consider, because the likes of PyLucene, Xapian, and others all have search related indices that then need to be kept up to date and available to the searcher processes. On 5/11/07, Jeremy Dunck <[EMAIL PROTECTED]> wrote: > > On 5/11/07, Ivan Sagalaev <[EMAIL PROTECTED]> wrote: > > > > - Am I doomed to have a separate server? This complicates things a lot > > and I very much inclined to use some in-process thing > > Probably. :) > > > - Are there any solutions on a scale between simplistic "likes" and > > sophisticated indexers like Lucene? > > http://www.osreviews.net/reviews/misc/hyperestraier > http://cheeseshop.python.org/pypi/estraiernative/0.2 > > http://swish-e.org/ > http://cheeseshop.python.org/pypi/Swish-E/0.5 > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
