Hi Fred,
I'm away from a pc until thursday, so I can't fix anything till
then, but perhaps you can check some things for me.
- Does this happen with every table? What about pg_class
for example?
- Does the table have any checks, foreign keys etc. on it.
- If you switch on the definition pane, what sql is generated
for the table?
As for the pg_ objects, yes they are obsolete now. pgAdmin
(original) has an option on the Advanced menu to remove
them all a bit more easily.
I'd also like to hear any comments you may have about the
new program...
regards, Dave.
--------------Replied message--------------
Date: Tue, 21 Aug 2001 09:49:39 -0500
From: fcy@acm.org
Sender: pgadmin-support-owner@postgresql.org
To: pgadmin-support@postgresql.org
Reply-To: fcy@acm.org
Subject: [pgadmin-support] can't access table properties in
1_1_20
Message-ID: <20010821094939.A1215@ontosys.com>
When I try to access "properties" of a table, either via the
right-button menu or the toolbar button, I get an alert titled
"pgAdmin II Error" saying
An error has occured in pgAdmin II:frmTable.Initialize:
Number: 457
Description: This key is already associated with an element
of
this collection.
A "Table" dialog window comes up, but it has no content in the
various
fields.
This is happening with pgAdmin II version 1.1 build 20 on an NT
4 SP 6
machine, accessing a PostgreSQL 7.1.2 server hosted on an NT
Cygwin
system.
I have used the older version of pgAdmin on this same database,
and it
worked well -- no obvious problems. There are pgadmin_*
objects
(tables, functions, views) in the database left over from that older
pgadmin. I tried removing all those objects, thinking that they
might
be obsolete, but that made no difference.
--
Fred Yankowski fred@OntoSys.com tel:
+1.630.879.1312
Principal Consultant www.OntoSys.com fax:
+1.630.879.1370
OntoSys, Inc 38W242 Deerpath Rd, Batavia, IL 60510,
USA
---------------------------(end of broadcast)---------------------------
TIP 4: Don't 'kill -9' the postmaster
