Changes between Initial Version and Version 1 of Ticket #32935, comment 8
- Timestamp:
- Nov 21, 2022, 7:03:16 AM (2 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #32935, comment 8
initial v1 1 Yes, InitSpatialMetaDataFull would remain as the preferred option. The fallback would be only for systems like Ubuntu 22.04 where using InitSpatialMetaDataFull per the docs is not an option, because the implementation in spatialite 5.0.1 (the latest released version) is incompatible with sqlite 3.36 (and newer versions). In spite of the stern warning on the PROJ.6 page, other parts of the documentation explain that InitSpatialMetaDataFull and InitSpatialMetaData are highly compatible:1 Yes, InitSpatialMetaDataFull would remain as the preferred option. The fallback would be only for systems like Ubuntu 22.04 where using InitSpatialMetaDataFull per the docs is not possible with the default packages, because the implementation in spatialite 5.0.1 (the latest released version) is incompatible with sqlite 3.36 (and newer versions). In spite of the stern warning on the PROJ.6 page, other parts of the documentation explain that InitSpatialMetaDataFull and InitSpatialMetaData are highly compatible: 2 2 3 3 https://www.gaia-gis.it/fossil/libspatialite/wiki?name=Upgrading+existing+DB-files+to+5.0.0 … … 17 17 except OperationalError as e: 18 18 if "ISO_metadata_reference_row_id_value_insert" in e.args[0]: 19 # Workaround for sqlite 3.36 and spatialite 5.0.120 cursor.execute("SELECT InitSpatialMetaData(1)")21 cursor.execute("SELECT CreateMissingSystemTables(1)")19 # Workaround for sqlite 3.36 and spatialite 5.0.1 20 cursor.execute("SELECT InitSpatialMetaData(1)") 21 cursor.execute("SELECT CreateMissingSystemTables(1)") 22 22 else: 23 23 raise