#15169: With gis.mysql backend BooleanField convert to Python as 1|0 instead of
True|False
-------------------------------+--------------------------------------------
Reporter: zmsmith | Owner: jbronn
Status: assigned | Milestone:
Component: GIS | Version: 1.2
Resolution: | Keywords: BooleanField, GIS,
Stage: Accepted | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
-------------------------------+--------------------------------------------
Changes (by jbronn):
* owner: nobody => jbronn
* status: new => assigned
Comment:
So, I wasn't aware that Django's MySQL backend got its own compiler module
last spring -- thus, proper subclasses need to be created in
`django.contrib.gis.db.backends.mysql.compiler`.
My initial patch fixes the problem, and moves the actual value conversion
in the MySQL backend to `convert_values` -- this is consistent with the
approach taken in Oracle's backend, and makes it easier for !GeoDjango to
use. However, this initial patch causes a regression in !GeoDjango's
`relatedapp` tests, but this could be related to #15040.
--
Ticket URL: <http://code.djangoproject.com/ticket/15169#comment:4>
Django <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 django-updates@googlegroups.com.
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
