On Monday 31 July 2006 11:04, Kevin wrote:
> My use of swish-e is clearly different that yours. The
indexer part of
> swish-e is run only periodically (say, nightly) with a
`swish-e -S prog
> -i ./generate_index.py`
>
> this creates an index file that the SwishE python api
queries....
Hey Kevin,
Yes, that's what I was planning on trying.
But, I was simply looking for a rule-of-thumb type answer to
"is swish-e a
better solution for searching about 10 million records than
using postgresql
native database queries" with the assumption that all
db queries are now
similar to "where upper(address) like '%123 MY
STREET%' and zipcode
like '%941%'"
I am expecting an answer like: "You are crazy: db
native searches will always
be faster" or maybe: "Swish-e will be faster if
you have to do "LIKE"
wildcard searches on many fields." I just want to
know if I'm in the
ballpark with thinking Swish-e, or other non-db searches
will be faster than
db-native searches.
Thanks,
Eric.
--
_________________________
Eric Walstad
740 Clementina Street
San Francisco, CA 94103
415-864-4224 voice & fax
eric ericwalstad.com
_________________________
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the
Google Groups "Django users" group.
To post to this group, send email to django-usersgooglegroups.com
To unsubscribe from this group, send email to
django-users-unsubscribegooglegroups.com
For more options, visit this group at http://gr
oups.google.com/group/django-users
-~----------~----~----~----~------~----~------~--~---
|