#32972: Django ORM raw query not playing nice with Geometric Point objects
-------------------------------------+-------------------------------------
Reporter: Donovan | Owner: nobody
Type: Bug | Status: closed
Component: GIS | Version: 3.2
Severity: Normal | Resolution: invalid
Keywords: ORM raw query | Triage Stage:
geometric location point | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Mariusz Felisiak):
* status: new => closed
* resolution: => invalid
Comment:
Using `.raw()` is a last resort. Django takes a raw SQL query, executes
it, and returns results (as documented), it will not automatically add any
data conversion to columns. Geometry columns returned by the ORM are
wrapped with db-specific functions, e.g. `%s::bytea` on PostgreSQL or
`SDO_UTIL.TO_WKBGEOMETRY(%s)` on Oracle.
If you're having trouble understanding how Django works, see
TicketClosingReasons/UseSupportChannels for ways to get help.
--
Ticket URL: <https://code.djangoproject.com/ticket/32972#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 unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/072.5ac68a6902cffa5094dfe0ab433dc0d3%40djangoproject.com.
