On Apr 24, 3:49 am, Joseph Kocherhans wrote:
> On Thu, Apr 23, 2009 at 6:50 PM, Ben Firshman wrote:
>
> > On 19 Apr 2009, at 11:42, mrts wrote:
>
> > > The feature is much needed, thanks for dealing with this!
>
> > > However, as for the API, I'd say coupling search to models is
> > > inadvisa
On Thu, Apr 23, 2009 at 6:50 PM, Ben Firshman wrote:
>
> On 19 Apr 2009, at 11:42, mrts wrote:
> >
> > The feature is much needed, thanks for dealing with this!
> >
> > However, as for the API, I'd say coupling search to models is
> > inadvisable, Django has moved away from that design.
> >
> > A
On 19 Apr 2009, at 11:42, mrts wrote:
>
> The feature is much needed, thanks for dealing with this!
>
> However, as for the API, I'd say coupling search to models is
> inadvisable, Django has moved away from that design.
>
> A registry-based approach could be implemented:
I agree this approach is
On Apr 19, 3:48 am, Ben Firshman wrote:
> This includes support for PostgreSQL in addition to MySQL, searching
> across multiple fields, automatic index creation, relevance, admin
> full text search and a simple generic search view. A brief example of
> the API:
>
> class Article(models.Mo
Hi all,
For Google's Summer of Code last year, I worked on djangosearch
(http://code.google.com/p/djangosearch/
) with the aim of extending it with more backends. It soon became
clear that the full text support in Django's database backends was
sufficient for most small sites. Considering t
