#8904: GeoDjango should raise a more informative exception when doing distance
queries on MySQL
---------------------------------------------+------------------------------
Reporter: robstar | Owner: jbronn
Status: new | Milestone:
Component: GIS | Version: 1.0
Resolution: | Keywords:
Stage: Design decision needed | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
---------------------------------------------+------------------------------
Changes (by jbronn):
* summary: geodjango should return more informative error for lack of
MySQL distance queries => GeoDjango should
raise a more informative exception when doing
distance queries on MySQL
* stage: Unreviewed => Design decision needed
--
Ticket URL: <http://code.djangoproject.com/ticket/8904#comment:2>
Django Code <http://code.djangoproject.com/>
The web framework for perfectionists with deadlines
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en
-~----------~----~----~----~------~----~------~--~---
