Changes between Initial Version and Version 1 of Ticket #953


Ignore:
Timestamp:
Dec 16, 2014, 7:19:25 AM (9 years ago)
Author:
Jukka Rahkonen
Comment:

From the documentation for GDAL 1.11.1 http://www.gdal.org/drv_odbc.html

By default the ODBC searches for GEOMETRY_COLUMNS table. If found it is used to identify the set of spatial tables that should be treated as layers by OGR. If not found, then all tables in the datasource are returned as non-spatial layers. However, if a table list (a list of comma seperated table names) is provided, then only those tables will be represented as layers (non-spatial). Fetching the full definition of all tables in a complicated database can be quite timeconsuming, so the ability to restrict the set of tables accessed is primarily a performance issue.

Issue seems to be fixed.

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #953

    • Property Status newclosed
    • Property Resolutionfixed