On 08/25/2010 02:19 PM, Sam Walters wrote:
I would need the answer evaluated as quickly as possible, radius calculation would be slower (how much slower depends on the algorithm used and other variables).
One of my colleagues tells me the database-internal (so: postgresql+postgis and so) calculations are lightning fast. Indexes optimized for it. So if you can keep the calculation inside the DB it ought to be fast enough.
I agree however that it's best not to have to work around this issue. So your fix-it-with-javascript idea might be best.
Reinout -- Reinout van Rees - rein...@vanrees.org - http://reinout.vanrees.org Collega's gezocht! Django/python vacature in Utrecht: http://tinyurl.com/35v34f9 -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
