Opened 12 years ago

Closed 12 years ago

Last modified 12 years ago

#2202 closed enhancement (fixed)

Using OCI + VRT to access non spatial data

Reported by: tamas Owned by: tamas
Priority: normal Milestone: 1.5.2
Component: OGR_SF Version: svn-trunk
Severity: normal Keywords:


In some cases the client would like OGR to access Oracle and extract point features based on x, y columns in non spatial tables. Currently the only option to do such things is to set up VRT+ODBC for the data access that would possibly result in the VRT-ODBC-OCI-Oracle data access path.

However not all of the clients can tolerate well the additional burden of installing an oracle-odbc driver and using additional system-wide settings to access their data. In addition it's sometimes not trivial to obtain oracle-odbc driver for a certain platform+processor achitecture at all (eg. linux + AMD64 in my case).

It would be reasonable to change the current OCI driver to provide access to tables without having Oracle Spatial to be installed. It would allow us to save the extra ODBC layer in the data access path mentioned above.

As looking into the OCI driver to support this would be almost all about removing the extra checks for the spatial data types in OGROCISession::EstablishSession?.

Change History (4)

comment:1 Changed 12 years ago by tamas

Committed in trunk r13705

comment:2 Changed 12 years ago by tamas

Resolution: fixed
Status: newclosed


comment:3 Changed 12 years ago by tamas

I had to make this additional change r13756

comment:4 Changed 12 years ago by tamas


Applied in branch 1.5 r13843

Note: See TracTickets for help on using tickets.