Bug report #6872
"ERROR: duplicate key value violates unique constraint "XXXX_pkey" always pops up when merging PostGIS features
| Status: | Closed | ||
|---|---|---|---|
| Priority: | Severe/Regression | ||
| Assignee: | - | ||
| Category: | Digitising | ||
| Affected QGIS version: | master | Regression?: | No |
| Operating System: | Easy fix?: | No | |
| Pull Request or Patch supplied: | No | Resolution: | duplicate |
| Crashes QGIS or corrupts data: | No | Copied to github as #: | 16002 |
Description
This is a regression in 1.8 and master since 1.7.4
Pick a PostGIS layer and select two features, then in the advanced editing toolbar use the "merge features" tool.
When saving edits you will always get a
ERROR: duplicate key value
violates unique constraint "XXXX_pkey"
like message.
The save operation usually goes ok anyway, but sometimes something very bad happens, and the merged features disappear completely without any notice.
Related issues
History
#1
Updated by Giovanni Manghi almost 12 years ago
Regarding the disappearing features, see: #6422
#2
Updated by Benedict Holland almost 12 years ago
I think I might be able to work on this bug but I don't have a PostGIS layer, or in this case 2. I am going to guess that there is something specifically setting the primary key with the merge instead of creating a new one. Can someone upload two PostGIS layers to merge as a test case?
~Ben
#3
Updated by Giovanni Manghi almost 12 years ago
Benedict Holland wrote:
I think I might be able to work on this bug but I don't have a PostGIS layer, or in this case 2. I am going to guess that there is something specifically setting the primary key with the merge instead of creating a new one. Can someone upload two PostGIS layers to merge as a test case?
I can provide you access (privately) to a test postgis server, but wouldn't be easier to install in your box PostgreSQL and PostGIS? Cheers.
#4
Updated by Jürgen Fischer almost 12 years ago
- Resolution set to duplicate
- Status changed from Open to Closed