Hi, well pgadmin sets table view in readonly mode if no Primary Key is defined.. That is more than a good practice from a DBA point of view, I wouldn't be against such a constraint for tables. We should raise some user warning when connecting to PG, so that users don't get confuzed Another point, what about views that do not have PK (but may be editable) ? Cheers Régis
-- View this message in context: http://osgeo-org.1560.x6.nabble.com/Strange-behaviour-in-feature-ids-when-editing-PostGIS-layer-tp5185929p5190614.html Sent from the Quantum GIS - Developer mailing list archive at Nabble.com. _______________________________________________ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
