From: | "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk> |
---|---|
To: | "Paul Wehr" <pgadmin(at)industrialsoftworks(dot)com>, <pgadmin-support(at)postgresql(dot)org> |
Subject: | Re: An error has occurred in pgAdmin II:frmMain.tvDatabases: |
Date: | 2002-07-16 07:03:27 |
Message-ID: | D85C66DA59BA044EB96AB9683819CF61137F4F@dogbert.vale-housing.co.uk |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-support |
> -----Original Message-----
> From: Paul Wehr [mailto:pgadmin(at)industrialsoftworks(dot)com]
> Sent: 15 July 2002 19:58
> To: pgadmin-support(at)postgresql(dot)org
> Subject: [pgadmin-support] An error has occurred in pgAdmin
> II:frmMain.tvDatabases:
>
>
> It did allow you to browse *some* of the tables (112/430),
> but now does not
> show any. Since it occured for multiple users
> simultaneously, it would
> seem more likely to be a server issue that a pgAdmin issue,
> but does anyone
> have any ideas?
Probably the quickest & easiest way to generate errors like that would
be to run pgAdmin 1.2.0 with PostgreSQL 7.3devel. The schemas in 7.3
will cause 1.2.0 big problems.
If this is the case, then the answer is easy, upgrade to pgAdmin 1.3.60.
If not, can you think what has changed on your database - any new
objects etc?
Regards, Dave.
From | Date | Subject | |
---|---|---|---|
Next Message | Carlos Leyn B. | 2002-07-16 15:11:46 | Problems with detail on relationships |
Previous Message | Paul Wehr | 2002-07-15 18:58:07 | An error has occurred in pgAdmin II:frmMain.tvDatabases: |