Hi,
2018-05-04 14:50 GMT+02:00 Martin Landa :
> ERROR 1: No column definitions found for table 'dbo.vla', layer not usable.
it's source of problems. Client fails to get column definitions [1].
Then GDAL tries to overwrite layer which fails [2].
Running SQL Server 2014.
Ma
[1] https://github.co
Hi Tamas,
2018-05-03 22:47 GMT+02:00 Tamas Szekeres :
first of all thanks for quick feedback!
> For some reason the table hasn't been found and the driver wanted to create
> a new table.
Right, seems to be like that.
> I've tried to reproduce this with a shapefile with no geometry uploaded to
Hi Martin,
For some reason the table hasn't been found and the driver wanted to create
a new table.
I've tried to reproduce this with a shapefile with no geometry uploaded to
MSSQL, but I couldn't.
Can I have your sample data? Which GDAL version has been used?
You could also check what happens by
Hi all,
let's assume sample data:
$ ogrinfo sample.gpkg
1: SOBR (Point)
2: VLA (None)
Append for geometry layers seems to work:
1) ogr2ogr -f MSSQLSpatial MSSQL:database=kn sample.gpkg sobr
->
1> select count(*) from sobr
2> go
---
5437
2) ogr2ogr -f MSSQLSpatial -append MSS
