On Apr 24, 3:49 am, Joseph Kocherhans <jkocherh...@gmail.com> wrote:
> On Thu, Apr 23, 2009 at 6:50 PM, Ben Firshman <b...@firshman.co.uk> 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 registry-based approach could be implemented:
>
> > I agree this approach is better for external engines, but when just
> > using SQL indexes, it makes a whole load of sense for it to be
> > included in the ORM. I see "search_index" as just an extension of
> > "db_index" and "unique".
>
> Not to mention GeoDjango's spatial_index argument. There's certainly prior
> art here. I agree that this approach would be entirely inappropriate for
> solr, xapian, whoosh, etc. but it makes sense for SQL. Ben and I have
> discussed this stuff at length over the last year, and I'm behind him 100%
> on the design.
Agreed, I had the impression that the generic API would be used for
both fulltext and SQL search.
If not, then you're of course right -- being a SQL feature, it should
be coupled to models.
Thanks for the work and good luck in bringing it into Django!
MS
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com
To unsubscribe from this group, send email to
django-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/django-developers?hl=en
-~----------~----~----~----~------~----~------~--~---
