Hi, It seems to work for other tables.
This table was one that was without OIDs, but had an int8 column accidentally named oid. It contained unique values, but neither this nor other columns were marked as UNIQUE nor PRIMARY KEY. Strange thing that seems to be related to the problem that primary keys have to be int4 and cannot be int8. So please lower this report to severity "wishlist", and change the request to: - Give better error messages in this case - Allow int8 (and other types?) for primary key columns - Allow the user to set a column as key column, whether or not it is declared as UNIQUE, PRIMARY KEY or OID. Maybe even a dropdown that contains all UNIQUE and PRIMARY KEY columns as well as OID if present, and a custom input field where desparate users can enter whatever they want. Btw, I just had a problem using an int4 column as label. When using the same data from a shape file, it works fine. But I'll do some more experiments on this. Thanks, Markus
signature.asc
Description: OpenPGP digital signature
