[Fdo-trac] [fdo-trac] #649: KingOracle Provider doesn’t work in Linux

[FDO]

#649: KingOracle Provider doesn’t work in Linux
-----------------------------------+----------------------
 Reporter:  rafael                 |        Owner:  haris
     Type:  defect                 |       Status:  closed
 Priority:  blocker                |    Milestone:  3.5.0
Component:  FDO API                |      Version:  3.5.0
 Severity:  3                      |   Resolution:  fixed
 Keywords:  Oracle FDO King Linux  |  External ID:
-----------------------------------+----------------------

Comment (by jng):

 In [changeset:"7814" 7814]:
 {{{
 #!CommitTicketReference repository="" revision="7814"
 Merged revision(s) 7811-7813 from trunk:
 Merged revision(s) 7790-7810 from sandbox/linux64shp:

 Fix up the SHP spatial index for 64-bit Linux. This makes the provider
 finally functional for FDO client applications like MapGuide on 64-bit
 Linux.

 Fixes #963
 ........
 Merged revision(s) 7766-7811 from sandbox/kgoralinux:

 Get King Oracle provider working on Linux. The root cause of why this
 provider did not work on Linux in the past is due to:

  a) wchar_t strings being garbage on Linux due to difference in platform
 size. Where wchar_t* strings are passed to OCI on Windows, they are now
 #ifdef'd (D_OCI_WIDE_STRINGS) on Linux to pass char* strings instead
  b) Possibly the use of OCINlsEnvCreate and OCILogon
    - I could not find a suitable OCI reference code on Linux that
 demonstrated the use of these 2 APIs.
    - So taking a page out of known OCI reference code (the OGR OCI
 driver), the provider uses OCIEnvCreate and OCIServerAttach on Linux for
 OCI setup and connection.

 This is backed by a new reproducible test suite that runs a basic set of
 provider test against an Oracle XE 11g instance. An 11g docker environment
 is provided to easily spin up such an environment.

 Fixes #649, #562
 ........
 Need to add TestCommon and ExpressionEngine projects to
 KingOracle_vs15.sln to ensure KgOraUnitTest will build in the correct
 configuration
 ........
 }}}

-- 
Ticket URL: <https://trac.osgeo.org/fdo/ticket/649#comment:3>
FDO <http://fdo.osgeo.org/>
Feature Data Objects