SQLite3+libspatialite diverged on Windows vs Unix #126
-
|
Write postgis data to the local Sqlite database using gdal, run it locally on Windows without any issues, and deploy it to a Linux Docker container with the following error: "SpatiaLite v4 DB found, but updating tables disabled because no linking against spatialite library!". How to solve this problem? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
|
The error clearly says that the sqlite3 library which is provided by VCPKG (and complied into bindings) is not linked against libspatialite. Windows behaviour differs and contains such extension because the binaries from GisInternals were used. On Unix systems we rely on VCPKG. For now I check only for this driver list and it's not possible to track every extension. This bindings won't support it, unless someone contributes and configures the pipeline to replace the sqlite3 library. |
Beta Was this translation helpful? Give feedback.
The error clearly says that the sqlite3 library which is provided by VCPKG (and complied into bindings) is not linked against libspatialite.
Windows behaviour differs and contains such extension because the binaries from GisInternals were used. On Unix systems we rely on VCPKG. For now I check only for this driver list and it's not possible to track every extension.
This bindings won't support it, unless someone contributes and configures the pipeline to replace the sqlite3 library.
If you need such functionality consider building against external sqlite3 which is linked against libspatialite.