Adam Endicott wrote: > > Do any of the core devs see this as a candidate for inclusion in > contrib?
Speaking as the author of the piece -- I don't. This code isn't developed enough to be particularly practical as-is: to be more useful it should probably support both natural language and boolean mode queries; it could perhaps also support multiple full text queries on one table. I don't know. At the very least it should support stemming. Bear in mind that I kept it as simple as possible so that it illustrated the essentials more clearly -- subclassing Manager and QuerySet, and building the extra parts of the SQL statement -- so the lack of features is intentional. But as the introduction states, the code in the paper is released into the public domain, so there's nothing stopping any interested person from taking it and developing it into something more suited for general searching. Andrew --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
