#10888: Inserting model with GeometryField as None crashes on Oracle
---------------------------------------------+------------------------------
Reporter: jtiai | Owner: jbronn
Status: new | Milestone:
Component: GIS | Version: SVN
Resolution: | Keywords: oracle gis null
Stage: Design decision needed | Has_patch: 0
Needs_docs: 0 | Needs_tests: 1
Needs_better_patch: 0 |
---------------------------------------------+------------------------------
Changes (by jbronn):
* keywords: oracle gis => oracle gis null
* owner: nobody => jbronn
* needs_tests: 0 => 1
* stage: Unreviewed => Design decision needed
Comment:
Replying to [comment:2 jtiai]:
For the rest of us,
[http://sourceforge.net/mailarchive/message.php?msg_name=49F050EC.30205%40gmail.com
this is the thread from the cx_Oracle mailing list].
> So this is now real problem since you cant have null geometries easily.
I agree it's a problem. But should we hack GeoDjango, as my attached
patch does to just use NULL for the placeholder and omit a parameter? Or
should we wait until the real underlying problem `cx_Oracle` is solved?
Until I'm convinced otherwise, I'm -1 on my own patch because (i) it's a
hack, (ii) needs tests and (iii) it does not address other `NULL` geometry
related issues, e.g., `UPDATE` queries (`.update(geom_field=None)`).
--
Ticket URL: <http://code.djangoproject.com/ticket/10888#comment:3>
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 [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
-~----------~----~----~----~------~----~------~--~---
