Changes between Initial Version and Version 3 of Ticket #4012


Ignore:
Timestamp:
Mar 23, 2011, 7:00:56 AM (13 years ago)
Author:
warmerdam
Comment:

I think that tables without geometry (ie. -nlt NONE) should *not* be in the geometry_columns table but perhaps we need some logic to avoid the failure you are seeing. I'm not planning on taking any action myself - I just wanted to put a stake in the ground with regard to non-spatial tables and geometry_columns.

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #4012

    • Property Keywords pg added
    • Property Owner changed from warmerdam to Even Rouault
    • Property Version unspecified → 1.8.0
    • Property Component default → OGR_SF

  • Ticket #4012 – Description

    initial v3  
    11The following command has different results in different versions of the driver:
     2{{{
    23ogr2ogr -f "PostgreSQL" %CS% "test.tab" -nlt NONE -nln test_table
     4}}}
    35where:
    4 - test.tab is a MapInfo file containing a non-spatial layer (just a regular table)
    5 - CS="PG:host='localhost' port='54321' dbname='test_ogr' user='test_ogr' password='test_ogr'"
     6 * test.tab is a MapInfo file containing a non-spatial layer (just a regular table)
     7 * CS="PG:host='localhost' port='54321' dbname='test_ogr' user='test_ogr' password='test_ogr'"
    68
    79In GDAL 1.7.1, released 2010/02/08, a record is inserted in geometry_columns.
    810But in both in:
    9 - GDAL 1.8.0, released 2011/01/12
    10 - GDAL 1.9dev, released 2011/01/18
     11 * GDAL 1.8.0, released 2011/01/12
     12 * GDAL 1.9dev, released 2011/01/18
     13
    1114no record is inserted.
    1215