Value in Primary Key Field with Sequence Is Ignored When New Feature Is Added #15181
Labels
Bug
Either a bug report, or a bug fix. Let's hope for the latter!
Data Provider
Related to specific vector, raster or mesh data providers
Author Name: Lee Hachadoorian (Lee Hachadoorian)
Original Redmine Issue: 5608
Affected QGIS version: master
Redmine category:data_provider/postgis
See thread [Qgis-user] QGis 1.7.4 possible bug with PostgreSQL/Postgis manual integer primary key? http://lists.osgeo.org/pipermail/qgis-user/2012-May/017113.html.
Steps to reproduce:
nextval() from sequence is a default value. Supplying a specific value via a manual INSERT statement or using pgAdmin edit grid respects user input. Therefore it appears that QGIS is programmed to ignore user-supplied value, resulting in default value supplied by sequence. This is inconsistent with other QGIS behavior in that QGIS allows user to edit existing primary key values and change them to any value which does not result in a key violation.
Desired behavior should be discussed. It seems the choices are (a) respect user input, or (b) do not allow user input.
Using QGIS 1.7.4 on Ubuntu 10.04, running against PostGIS 1.4/PostgreSQL 8.4.
The text was updated successfully, but these errors were encountered: