#16556 closed Bug (duplicate)
django.contrib.gis.utils.srs fails to preserve database when creating SpatialRefSys querysets
Reported by: | anonymous | Owned by: | jbronn |
---|---|---|---|
Component: | GIS | Version: | 1.3 |
Severity: | Normal | Keywords: | |
Cc: | Triage Stage: | Accepted | |
Has patch: | no | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | no |
Easy pickings: | no | UI/UX: | no |
Description (last modified by )
django.contrib.gis.utils.srs
fails to preserve database when creating SpatialRefSys
querysets
Currently, the code (line ~70 or so) reads like this:
# Creating the spatial_ref_sys model. try: # Try getting via SRID only, because using all kwargs may # differ from exact wkt/proj in database. sr = SpatialRefSys.objects.get(srid=srs.srid) except SpatialRefSys.DoesNotExist: sr = SpatialRefSys.objects.create(**kwargs)
It should read like this:
# Creating the spatial_ref_sys model. try: # Try getting via SRID only, because using all kwargs may # differ from exact wkt/proj in database. sr = SpatialRefSys.objects.using(database).get(srid=srs.srid) except SpatialRefSys.DoesNotExist: sr = SpatialRefSys.objects.using(database).create(**kwargs)
Otherwise support for multiple backends is sort of broken.
Attachments (1)
Change History (5)
comment:1 by , 13 years ago
comment:2 by , 13 years ago
Description: | modified (diff) |
---|---|
milestone: | → 1.4 |
Owner: | changed from | to
Status: | new → assigned |
Triage Stage: | Unreviewed → Accepted |
comment:3 by , 13 years ago
Resolution: | → duplicate |
---|---|
Status: | assigned → closed |
This is a duplicate of #16537. Please search before opening a new ticket — here, it's completely trivial to find the duplicate: https://code.djangoproject.com/search?q=SpatialRefSys&noquickjump=1&ticket=on
Note:
See TracTickets
for help on using tickets.
Ugh. Basically, the '.using()' method needs to be used when creating the SpatialRefSys query set. sorry for the poor formatting.