Bug report #16297
(macOS) layers imported into a Spatialite Database with DB manager are not recognized as spatial tables
| Status: | Closed | ||
|---|---|---|---|
| Priority: | High | ||
| Assignee: | - | ||
| Category: | DB Manager | ||
| Affected QGIS version: | 2.18.2 | Regression?: | Yes |
| Operating System: | macOS | Easy fix?: | No |
| Pull Request or Patch supplied: | No | Resolution: | fixed/implemented |
| Crashes QGIS or corrupts data: | No | Copied to github as #: | 24207 |
Description
This has been seen on QGIS 2.18.4 on macOS. The same seems ok on other platforms.
It was also ok on macOS with 2.14.*
After importing a layer into a SL database within DB Manager (with d&d or by using the "import layer/file" tool) the resulting table is NOT recognized as a spatial one.
Importing the same layer using the browser d&d produces the expected result.
History
#1
Updated by Giovanni Manghi over 7 years ago
- Regression? set to Yes
#2
Updated by Giovanni Manghi over 7 years ago
- Priority changed from Severe/Regression to High
#3
Updated by Giovanni Manghi over 7 years ago
- Easy fix? set to No
#4
Updated by Giovanni Manghi over 7 years ago
- Resolution set to fixed/implemented
- Status changed from Open to Closed
- Description updated (diff)
Works as expected with 2.18.7 installed from brew on 10.12.4