> -----Original Message-----
> From: George T. Gibson [mailto:[EMAIL PROTECTED]
> Sent: 10 July 2003 20:33
> To: [EMAIL PROTECTED]
> Subject: [pgadmin-support] pgadminIII bug
>
>
> When trying to alter a sequence value, the below SQL is issued...
>
> SELECT setval(public.part_part_id_key, 3479);
>
> Then I get...
>
> ERROR: Relation "public" does not exist
Thanks George, fixed in CVS.
Regards, Dave.
---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match