[Fdo-trac] [fdo-trac] #937: OGR Provider: Better support for VRT data sources

[FDO]

#937: OGR Provider: Better support for VRT data sources
--------------------------+------------------------
 Reporter:  jng           |        Owner:  jng
     Type:  defect        |       Status:  assigned
 Priority:  major         |    Milestone:
Component:  OGR Provider  |      Version:
 Severity:  3             |   Resolution:
 Keywords:                |  External ID:
--------------------------+------------------------
Description changed by jng:

Old description:

> The current OGR provider has some issues around VRT data sources:
>
>  * Invalid VRTs do not bubble up as FDO exceptions because we're not
> checking `CPLGetLastErrorMsg()` for any logged errors during the
> `OGRLayer` -> `FdoClassDefinition` conversion process
>  * SQL layers that involve table aliases produces property names of the
> form `{table_name}.{column_name}`. This is illegal in FDO as dots are
> forbidden in property names.

New description:

 The current OGR provider has some issues around VRT data sources:

  * Invalid VRTs do not bubble up as FDO exceptions because we're not
 checking `CPLGetLastErrorMsg()` for any logged errors during the
 `OGRLayer` -> `FdoClassDefinition` conversion process
     * As a general theme: There are many cases in the OGR provider where
 we are failing to check `CPLGetLastErrorMsg()` after an API call
  * SQL layers that involve table aliases produces property names of the
 form `{table_name}.{column_name}`. This is illegal in FDO as dots are
 forbidden in property names.

--

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