![]() SELECT DropTable('some_db', 'some_table') ![]() If SpatiaLite is running against an earlier version both functions will always raise an Exception complaining about the mismatching library version. Let's now see each single SQL function in full details.īoth RenameTable() and RenameColumn() strictly require SQLite3 version 3.25.0 (or greater). More information and practical samples on how to explicitly define columns can be found here: SQLite: CREATE VIEW syntax explicitly declaring columns.Unofficially, any Column not explicitly defined is considered undefined and SQLite will attempt to resolve the old name by looking inside the underlaying TABLE.The explicit declaration of Columns in the CREATE VIEW is (officially) optional.Special Note: SQLite CREATE VIEW syntax explicitly declaring columns:.Will also work on ordinary (non Spatial) Columns, GeoPackage and OGR/FDO Geometries. VIEWs: only the Column-name of the underlaying TABLE used by the VIEW will be renamed.RenameColumn(): can safely rename a Spatial (or non-Spatial), but cannot be used for any kind of View or VirtualTable.Īny depending Trigger, View, Spatial Index, Metadata and Statistics will be properly updated fully preserving the DB layout consistency.This will also work on any ordinary (non Spatial) Table, RasterLite2 Raster Coverage, GeoPackage and OGR/FDO Table. VIEWs: only the name of the underlaying TABLE used by the VIEW will be renamed.RenameTable(): can safely rename a Spatial (or non-Spatial) Table, but cannot be used for any kind of View or VirtualTable.Īny dependent Triggers, Views, Spatial Indexes, Metadata and Statistics will be properly updated fully preserving the DB layout consistency. ![]() ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |