[Gdal-dev] SQLite problem

[Even Rouault]

I can read output2.sqlite with ogrinfo:

INFO: Open of `output2.sqlite'
      using driver `SQLite' successful.

Layer name: output
Geometry: Point
Feature Count: 2
Extent: (13.000000, 38.000000) - (13.500000, 39.000000)
Layer SRS WKT:
GEOGCS["WGS 84",
    DATUM["WGS_1984",
        SPHEROID["WGS 84",6378137,298.257223563,
            AUTHORITY["EPSG","7030"]],
        AUTHORITY["EPSG","6326"]],
    PRIMEM["Greenwich",0,
        AUTHORITY["EPSG","8901"]],
    UNIT["degree",0.01745329251994328,
        AUTHORITY["EPSG","9122"]],
    AUTHORITY["EPSG","4326"]]
id: String (0.0)
testo: String (0.0)
xi: String (0.0)
yi: String (0.0)
test: String (0.0)
OGRFeature(output):1
  id (String) = 1
  testo (String) = ciao
  xi (String) = 13.000000
  yi (String) = 38.000000
  test (String) = (null)
  POINT (13 38)

OGRFeature(output):2
  id (String) = 2
  testo (String) = bau
  xi (String) = 13.500000
  yi (String) = 39.000000
  test (String) = (null)
  POINT (13.499999999999996 39.0)


I believe having read somewhere that old versions of sqlite libraries didn't 
handle well changing the structure of a table after its creation. Is there 
any chance that your GDAL build links to an old sqlite library ?

Le Wednesday 29 October 2008 23:39:19 iomeneandrei, vous avez écrit :
> Hi Frank,
> thank you very much.
>
> Frank Warmerdam-2 wrote:
> > The file you referenced seems to work fine with my (trunk) ogrinfo.  Can
> > you
> > provide an example that ogrinfo can't read?  Generally, adding new
> > columns to
> > a spatial table should not cause problems for OGR.
>
> The file I have attache was the right one.
> I have used this query:
> ALTER TABLE "main"."output" ADD COLUMN "test" VARCHAR
>
> And I have had the file I'm attaching now
> http://www.nabble.com/file/p20237327/output2.sqlite output2.sqlite .
>
> I'm not able to read it with ogrinfo.
>
> My sqlite client is this:
> https://addons.mozilla.org/en-US/firefox/addon/5817
>
> Thank you,
>
> Andrea
>
> -----
> Andrea Borruso
>
> ----------------------------------------------------
> email: aborruso at tin.it
> blog: http://blog.spaziogis.it
> ----------------------------------------------------