Please sign in to comment.
New run_sanity_checks mechanism, for SpatiLite
Moved VirtualSpatialIndex check into a new mechanism that should allow us to add further sanity checks in the future. To test this I've had to commit a binary sample SpatiaLite database to the repository. I included a build script for creating that database. Closes #466
- Loading branch information...
Showing with 68 additions and 26 deletions.
|@@ -0,0 +1,23 @@|
|# This script generates the spatialite.db file in our tests directory.|
|conn = sqlite3.connect(filename)|
|# Lead the spatialite extension:|
|conn.executescript("create table museums (name text)")|
|conn.execute("SELECT AddGeometryColumn('museums', 'point_geom', 4326, 'POINT', 2);")|
|# At this point it is around 5MB - we can shrink it dramatically by doing thisO|
|conn.execute("delete from spatial_ref_sys")|
|conn.execute("delete from spatial_ref_sys_aux")|
|if __name__ == "__main__":|
BIN +216 KB tests/spatialite.db
Binary file not shown.