Bug report #16297
Updated by Giovanni Manghi almost 7 years ago
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.
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.