> Finally,
> I want to provide users the ability to search for nearby posts or
> within a certain boundary (from the documentation I've read, this is
> what GeoDjango apparently excels at).
that's the point. it seems easy, until you write some SQL to express
the 'nearby' criteria... and find that you're doing a very expensive
full-table scan.
a GIS database handles spatial indexes, so queries like "order by
distance to this point, retrieve the 20 closest" or "all points inside
this polygon" are done quickly and efficiently no matter the number of
points in the database.
Postgres and SQLite handle these type or queries; some MySQL versions
can deal a few of them. better go with Postgres, as it's far more
tested (and used by core developers)
--
Javier
--
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 django-users+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
No comments:
Post a Comment