Bug report #17186
DB Manager and QGIS/Processing import in PostGIS tools are not adding "nextval()" to primary key field
|Affected QGIS version:||2.18.13||Regression?:||No|
|Operating System:||Easy fix?:||Yes|
|Pull Request or Patch supplied:||No||Resolution:||worksforme|
|Crashes QGIS or corrupts data:||No||Copied to github as #:||25085|
D&D in browser (from shapefile for example) and the ogr based tool in processing do the right thing.
The PostGIS data provider seems to add only the PK
Without nextval(), beside not being very handy is also very easy to get bigger problems, like #17185
#5 Updated by Alessandro Pasotti almost 3 years ago
- Category changed from Data Provider/PostGIS to DB Manager
I verified in master and there is nothing buggy in the provider itself (when D&D from the browser the nextval() is created correctly, I suspect that the issue is in how dbmanager handles that.