Ari Jolma kirjoitti 9.4.2020 klo 17.23:
Same outcome.
There's something very strage going on as the max of the id is 305926
(after creating the table with the first gpkg) but when I try to
manually insert a row to the table it says "key id=39 already exists".
If I then manually setval the seq
Same outcome.
There's something very strage going on as the max of the id is 305926
(after creating the table with the first gpkg) but when I try to
manually insert a row to the table it says "key id=39 already exists".
If I then manually setval the sequence to 305926 I can add to the table.
Hi,
I would have a try with -unsetfid. That should be the default when in append
mode but the test is easy.
-Jukka Rahkonen-
Ari Jolma-2 wrote
> I have this command
>
> ogr2ogr -update -append -f PostgreSQL PG:... merged.gpkg
>
> which works ok in version 3.0.2 (self-compiled) but not in 2.2.
Even,
You are right. I wouldn't use the double /vsi in gdal_translate. It just
happened that I found a corrupted file on tile x33y13 date 2013/249 and I
wanted to know if I could pass the gdalinfo command to other people. I will
download same sample files, run gdalinfo on my machine and copy a
I have this command
ogr2ogr -update -append -f PostgreSQL PG:... merged.gpkg
which works ok in version 3.0.2 (self-compiled) but not in 2.2.3 (from
ubuntu apt). The error is
ERROR: duplicate key value violates unique constraint "stand_pkey"
DETAIL: Key (id)=(1) already exists.
CONTEXT: COPY s
