[postgis-users] Missing primary key column. (SOLVED)

[Byron Como]

Ben has the solution.

Indeed, the geometry column primary key was messed up. I deleted the old 
one, added the gid serial integer column and set it to the primary key. 
Works like a charm.

On 1/8/2011 5:11 PM, Ben Madin wrote:
> Byron,
>
> A little bit more information may help here - what do you mean by 'importing' the table into QGIS? Have you checked that the primary key is unique - and such a constraint exists on the table definition? and that the column is in the geometry_columns table - you may want to try populate_geometry_columns() function.
>
> maybe post the output of \d tablename.
>
> cheers
>
> Ben
>
> On 09/01/2011, at 9:46 AM, Byron Como wrote:
>
>> The problem:
>> Missing primary key column in postgresql table imported into Quantum GIS.
>>
>> Details:
>> 43,000 object database created using Windows XP 32 bit, postgresql 8.4, postgis 1.4, Quantum GIS 1.5.
>> Daily backups using pgadmin.
>> Several db restores were performed on the XP system for various reasons (one time was to recover from a lightning strike). Restored data was good and project continued with no problems.
>> Recently upgraded to Windows 7 64 bit to be current and take advantage of the increased memory available.
>> Installed the same software as above.
>> The data in postgresql seems ok and can be manipulated normally - copied, pasted, deleted.
>> Importing a table into Qgis 1.5 or 1.6 results in layer with the primary key column missing. The data can't be manipulated completely. The table can be added to but deletions can't be performed. The primary key is gid, integer.
>>
>> Corrective actions thus far:
>> Reloaded software many times giving great attention to the details of installation. Examined the data in pgadmin for anomalies. Nothing apparent. All seems correct. Posted to Quantum GIS mailing list. Nothing there.
>>
>> Expected resolution:
>> Barring solution from mailing list suggestions, reinstall on Windows XP 32 bit and continue with memory limitations as before. (Extra memory desired to make very large format high-resolution prints).
>>
>> _______________________________________________
>> postgis-users mailing list
>> postgis-users at postgis.refractions.net
>> http://postgis.refractions.net/mailman/listinfo/postgis-users
> _______________________________________________
> postgis-users mailing list
> postgis-users at postgis.refractions.net
> http://postgis.refractions.net/mailman/listinfo/postgis-users
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/postgis-users/attachments/20110108/6661e0e9/attachment.html>