Please sign in to comment.
Use sqlite3 to directly run some SQL queries in QgsSpatiaLiteProvider…
…Connection, where we don't require result rows Because GDAL runs some consistency checks on spatialite databases on opening, this breaks the multi-step SQL commands which are run as part of renameVectorTable. The first SQL renames the table, then when the second tries to run gdal rejects the database because the geometry_columns definition is corrupt. Instead, add a method to directly run sql commands using sqlite3 instead of GDAL, and use this to run any SQL where we don't require result rows. Fixes Spatialite connection test
- Loading branch information
Showing with 28 additions and 5 deletions.