Opened 5 years ago

Last modified 4 years ago

#937 closed defect

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

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

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.

Change History (0)

Note: See TracTickets for help on using tickets.