#5498: GeoDjango not compatible with PostGIS 1.1.0
--------------------------------------------+-------------------------------
Reporter: jbronn | Owner: jbronn
Status: new | Component: GIS
Version: gis | Resolution:
Keywords: gis sprint geodjango postgis | Stage: Accepted
Has_patch: 1 | Needs_docs: 0
Needs_tests: 0 | Needs_better_patch: 0
--------------------------------------------+-------------------------------
Comment (by jbronn):
Replying to [comment:1 rcoup]:
> I can't see where `GEOSGeometry.getquoted()` is ever used, and I'm
reluctant to add `GEOM_FUNC_PREFIX` because it'll then couple GEOS to the
postgis backend
`GEOSGeometry.getquoted()` is only used by the psycopg2 adapter. When
psycopg2 sees an object in its parameters (''e.g.'', `execute(sql,
params)`), it checks to see if it has the `__conform__` method, and uses
the `getquoted` routine for the quoting of the object for PostgreSQL.
I'm with you on the GEOS dependency issue -- I always attempt to keep the
GEOS module as loosely coupled as possible. I will most likely place the
import in a try/except to maintain this (nothing will be broken since it's
only needed when used w/postgres).
--
Ticket URL: <http://code.djangoproject.com/ticket/5498#comment:3>
Django Code <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 [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
-~----------~----~----~----~------~----~------~--~---
