I've been working on enabling search on a django application, and we found an interesting problem in having two head-end machines serving our content. That was basically - how do we keep the indices up to date and intact for the relevant data? (We wanted the search pieces *immediately* available upon save into the DB).
We considered using NFS to mount a common file system, but ultimately decided to use TSearch2 (a plugin to Postgres) since we were already using Postgres and the notes that I saw about threading and PyLucene with Apache/Mod_Python were looking "kinda scary" (yes, a victim of FUD in this case). Xapian looked very intriguing, but "where do I put the inverted index file" issue as well. -joe On 1/7/07, Tim Keating <[EMAIL PROTECTED]> wrote:
I was wondering whether I could just grab django/contrib/search, and now I know. Thanks! I'll give that a shot. Given that workaround, I wouldn't worry about a downmerge right now, I know how time-consuming they are. TK >
--~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
