Bug report #13341
DBManager doesn't import view from table with non numeric key
|Affected QGIS version:||master||Regression?:||No|
|Operating System:||Easy fix?:||No|
|Pull Request or Patch supplied:||No||Resolution:||end of life|
|Crashes QGIS or corrupts data:||No||Copied to github as #:||21394|
DBManager can import without any problem PostGIS geometries with non numeric Primary Key.
When a view is made from a such kind of table:
CREATE OR REPLACE VIEW my_schema.my_view AS
SELECT * FROM my_schema.my_table;
it can be imported correctly using the tool 'Add PostGIS layer' (after choosing the primary key column).
DBManager doesn't display the geometry in the preview window, and when trying to import it alerts 'The layer is not a valid layer and can not be added to the map'.
I've already seen Bug report #11317; the problem is related to DBManager, since QGIS can manage it, so it doesn't depend on unique key.
#5 Updated by Giovanni Manghi over 2 years ago
- Resolution set to end of life
- Status changed from Open to Closed
End of life notice: QGIS 2.18 LTR