> /As far as I can see now that's the main problem: not having a OID field.
> Furthermore it should not be an issue of Pmapper because I had the same
> problem when testing it in Chameleon. On a mailinglist one mentioned also the
> unique-field that should cause the problem. I tried other exist
bram wrote:
>> I tried to make a connection to a postgresql-table within pmapper1.0.8
>> as well al in pmapper2 (both dated 2006-02-20). I work on a
>> windows-machine with Firefox. The connections succeeded, the masp were
>> drawn, but when retrieving info with 'identify' or with 'select' w
bram wrote:
> I tried to make a connection to a postgresql-table within pmapper1.0.8
> as well al in pmapper2 (both dated 2006-02-20). I work on a
> windows-machine with Firefox. The connections succeeded, the masp were
> drawn, but when retrieving info with 'identify' or with 'select' we
>
I tried to make a connection to a postgresql-table within pmapper1.0.8
as well al in pmapper2 (both dated 2006-02-20). I work on a
windows-machine with Firefox. The connections succeeded, the masp were
drawn, but when retrieving info with 'identify' or with 'select' we
see the correct number
