#15295: GeoDjango model creation fails for MySQL during tests
--------------------------------------+------------------------
Reporter: adamnelson | Owner: nobody
Type: Bug | Status: closed
Milestone: | Component: GIS
Version: SVN | Severity: Normal
Resolution: wontfix | Keywords:
Triage Stage: Accepted | Has patch: 0
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
--------------------------------------+------------------------
Comment (by adamnelson):
It's not efficient to use !GeoDjango with range queries on InnoDB (because
of the lack of SPATIAL indexes) but it works exactly the same as MyISAM
with regards to point() fields.
I'm fine keeping this ticket closed, but !GeoDjango does work with InnoDB
and in addition it's not documented anywhere that !GeoDjango is not
supported on InnoDB.
--
Ticket URL: <https://code.djangoproject.com/ticket/15295#comment:6>
Django <https://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.
