Hi EDven,
I try to use the your patch with gdal and mapserer.
Now I'm able to choose the right geometry from a multi-geometry table.
also I see that using this sintax
CONNECTIONTYPE OGR
CONNECTION '/path-to-splite/database.sqlite'
DATA "select pk_uid,field1,field2,field3,geometry from
Hi Roualt,
thx for patch,
I'm go to test it.
Just a question to understand how use it.
the sintax 'TABLE(GEOMETRY)' should return also the attributes from table
or only the geometry without attribute ?
regards,
--
-
Andrea Peri
. . . . . . . . .
qwerty àèìòù
-
Andrea created http://trac.osgeo.org/gdal/ticket/4768 and I've just committed
the code in trunk to add that support. I've tested it with a tiny sample just
made for the unit test. No reason it should not work with more complex DBs,
but testing appreciated.
___
Selon Jukka Rahkonen :
Multi geometry support per table isn't really supported for now. For the PG
driver, we expose layer names as "table_name(geometry_column_name)". I think the
same convention could be used for sqlite. In your example, it would be
"multigeom(geom1)" and "multigeom(geom2)". The
Hi,
A Mapserver user was trying to use a Spatialite db which had tables with
multiple geometry columns and I got interested in having a little try because
sometimes it could be handy to have both the polygons and their centroids
readily available from the same table.
However, it looks that curren
