Hi,
We ran exactly same situation and we actually wrote did a slightly different
solution - we now do have (yet to be opensourced) a backend that actually reads
SDO_GEOMETRY directly and writes a string that resembles SDO_GEOMETRY and is
parsed to real SDO_GEOMETRY with small PL/SQL package uti
Hi Michael,
At least, I found nothing shocking in your patches, so in my
non-oracle-savvy eyes, this looks rather fine. It would then be interesting
to see if some tests from django.contrib.gis.tests.geo3d.tests can pass
with Oracle.
Please create a ticket and link a pull request with your prop
Hi
I have recently started using Django and tried to use it with our legacy Oracle
Spatial database. The geometries we store in Oracle are all 3D and as such
don’t work with Django. It boils down to this:
select sdo_util.to_wktgeometry(sdo_geometry(3001, null, SDO_POINT_TYPE(120,-30,
0), null,
