Bug report #8284
Can not drag and drop layers to Spatialite in DB Manager
Status: | Closed | ||
---|---|---|---|
Priority: | Severe/Regression | ||
Assignee: | - | ||
Category: | DB Manager | ||
Affected QGIS version: | master | Regression?: | No |
Operating System: | Easy fix?: | No | |
Pull Request or Patch supplied: | No | Resolution: | fixed |
Crashes QGIS or corrupts data: | No | Copied to github as #: | 17084 |
Description
Running OS X 1.8.3 with nightly build from Dakota Cartographic. The build uses SpatiaLite 4. Drag and drop works very well with QGIS 1.8 (SpatiaLite 3).
Dragging either a PostgreSQL or SpatiaLite layer to a SpatiaLite database in DB Manager fails. Get dialog showing "Unable to load layer <built in method name of QgsVectorLayer object at 0x12353cf80>".
Debug information shows the following: src/core/qgsvectorlayer.cpp: 188: (~QgsVectorLayer) entered. src/core/qgsmaplayer.cpp: 58: (QgsMapLayer) original name: 'sacatalog' src/core/qgsmaplayer.cpp: 60: (QgsMapLayer) display name: 'sacatalog' src/core/qgsproviderregistry.cpp: 336: (provider) Library name is /Applications/QGIS_2.0-dev.app/Contents/MacOS/../PlugIns/qgis/libspatialiteprovider.so src/providers/spatialite/qgsspatialiteprovider.cpp: 4064: (openDb) New sqlite connection for /Volumes/PROMISE_PEGASUS/mapping/GIS/soils2/soilsSE_20130706.sqlite src/providers/spatialite/qgsspatialiteprovider.cpp: 4085: (openDb) Connection to the database was successful src/providers/spatialite/qgsspatialiteprovider.cpp: 487: (QgsSpatiaLiteProvider) Invalid SpatiaLite layer src/core/qgsproviderregistry.cpp: 358: (provider) Instantiated the data provider plugin: spatialite src/core/qgsvectorlayer.cpp: 1612: (setDataProvider) Instantiated the data provider plugin src/core/qgsvectorlayer.cpp: 1687: (setDataProvider) Invalid provider plugin dbname='/Volumes/PROMISE_PEGASUS/mapping/GIS/soils2/soilsSE_20130706.sqlite' table="sacatalog" () sql=
History
#1 Updated by Jürgen Fischer over 11 years ago
- Resolution set to fixed
- Status changed from Open to Closed
also fixed by cafc367