#16537: layermapping spatial ref check not checking against alternate DB
---------------------------------------------+------------------------
Reporter: shifflett.shane@… | Owner: nobody
Type: Bug | Status: new
Milestone: | Component: GIS
Version: 1.3 | Severity: Normal
Resolution: | Keywords:
Triage Stage: Accepted | Has patch: 1
Needs documentation: 0 | Needs tests: 1
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
---------------------------------------------+------------------------
Changes (by aaugustin):
* needs_better_patch: => 0
* stage: Unreviewed => Accepted
* easy: 1 => 0
* needs_tests: => 1
* needs_docs: => 0
Comment:
This line dates back to the merge of multi-db at r11952, but it was
changed because of the general refactoring of django.contrib.gis that
happened in that commit, not specifically to add multi-db support.
A similar problem was fixed in django/contrib/gis/db/models/fields.py at
r12258.
I think the problem also happens in django/contrib/gis/utils/srs.py. I'm
attaching a new patch that also fixes this. This patch is based on code
inspection and isn't tested.
--
Ticket URL: <https://code.djangoproject.com/ticket/16537#comment:1>
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 this group at
http://groups.google.com/group/django-updates?hl=en.
