Hi,
I just produced and error message when trying to drop a constraint on a table
which is in a schema with a mixed-case name.
---
pgAdmin III
---
An error has occurred:
ERROR: schema "mycomponent" does not exist
---
OK
I'd be in favour
of removing the distinction - a few people have asked me about the difference.
> It's a historic thing - procedures actually appeared in
> early versions
of EnterpriseDB originally where they were
> considered different objects
from functions if memory
> serves. The distinction
I see this as well, Win XP, pgAdmin 1.6.1, Postgres 8.2.
Cheers.
>In v1.6.1, when I go to view the data for a table with no (zero)
rows, I don't see the columns of the table and no place to key a new
record. The table does >have a primary key, and when it's got rows
in, I can edit and add new
