[QGIS-trac] Re: [Quantum GIS] #1535: qgspostgresprovider choosing non-unique column as primary key

[Quantum GIS]

#1535: qgspostgresprovider choosing non-unique column as primary key
-----------------------------------------------------+----------------------
        Reporter:  jcs                               |         Owner:  nobody       
            Type:  bug                               |        Status:  new          
        Priority:  major: does not work as expected  |     Milestone:  Version 1.0.1
       Component:  Data Provider                     |       Version:  0.10.0       
      Resolution:                                    |      Keywords:  postgres     
Platform_version:                                    |      Platform:  All          
        Must_fix:  No                                |   Status_info:  0            
-----------------------------------------------------+----------------------
Comment (by jcs):

 after a little more code diving...

 the above case will be caught by uniqueData() if and only if the tables
 are initialized before the layer is created.  if in a dynamic situation
 where the tables are initialized after the layer is created, the error
 condition still exists.

 i still think a better resolution is to catch the join and rule out any of
 those columns as you cannot be sure they will not one day become non-
 unique.

-- 
Ticket URL: <https://trac.osgeo.org/qgis/ticket/1535#comment:1>
Quantum GIS <http://qgis.org>
Quantum GIS is an Open Source GIS viewer/editor supporting OGR, PostGIS, and GRASS formats