Opened 5 years ago

Last modified 5 years ago

#937 closed defect

OGR Provider: Better support for VRT data sources — at Version 1

Reported by: jng Owned by: jng
Priority: major Milestone:
Component: OGR Provider Version:
Severity: 3 Keywords:
Cc: External ID:

Description (last modified by jng)

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.

Change History (1)

comment:1 by jng, 5 years ago

Description: modified (diff)
Note: See TracTickets for help on using tickets.