#15295: GeoDjango model creation fails for MySQL during tests
----------------------------+------------------------------------
Reporter: adamnelson | Owner: nobody
Type: Bug | Status: new
Component: GIS | Version: master
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
----------------------------+------------------------------------
Changes (by Cerin):
* status: closed => new
* resolution: wontfix =>
Comment:
Please re-consider this bug. It effects a lot more than just tests. As
most people use Innodb with MySQL, this effectively makes all
django.contrib.gis functionality incredibly awkward to most MySQL users,
if not completely inaccessible. Slower functionality due to missing
indexes on Innodb is preferrable to no functionality whatsoever.
It should at least be mentioned in the docs somewhere that GeoDjango has
not support for InnoDB. I wasted several hours going over the docs and
through the setup only to realize I couldn't use any of it with my pre-
existing InnoDB database when my initial model migrations blew up.
--
Ticket URL: <https://code.djangoproject.com/ticket/15295#comment:7>
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 django-updates@googlegroups.com.
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
