Re: [gdal-dev] Implications of "Multi-column primary key in [table] to supported" warning

2022-03-04 Thread DUTRIEUX Loic
Thanks for the many insights Jukka, it has helped me a lot in thinking where to dig and what to look at. First, and this is what matters the most to me, I was able to confirm data integrity by comparing for each table the pg version to the sqlite version. Some types are altered (e.g. Dates

Re: [gdal-dev] Implications of "Multi-column primary key in [table] to supported" warning

2022-03-03 Thread Rahkonen Jukka (MML)
Hi, If you have a table with multi-column primary key (composite key) then the target table in Spatialite obviously will not have the same PK. I would guess that none of the columns in the composite is unique and usable as PK so the only possibility is to create a new unique column for the PK.

[gdal-dev] Implications of "Multi-column primary key in [table] to supported" warning

2022-03-03 Thread DUTRIEUX Loic
Hi everyone, Quick question, I'm using ogr2ogr to clone a postGIS database to a spatialite file database (by the way, very convenient that ogr2ogr handles the transfer of non-spatial tables too). The database contains many-to-many relations and as a consequence association tables with multiple