It's the environment restauration that triggers this; the database node will perform the check.
-----Original Message-----
From: Andreas Pflug [mailto:[EMAIL PROTECTED] Sent: 19 November 2003 22:56
To: Dave Page
Cc: Michael Shapiro; [EMAIL PROTECTED]
Subject: Re: [pgadmin-support] pgAdmin bug? snapshot
Stop!!!!
This is not the code for dependency! This is the "old constraint trigger" detector code, which shows non-converted (pre-7.3) constraint triggers.
I added this as a response to "where are my triggers, pgadmin2 showed them all right" claims.
Yes, I realise what it is, but presumably it is only being run at that point because the dep code has caused that part of the tree to be built?
Or are you not using the data structure behind the treeview as a cache like we did in pga2? It strikes me that it also might be the environment restoration causing it this time, though I didn't realise it restored deeper than the schema.
The dependency code evaluates each node independently from the tree, and will not iterate any client nodes.
Regards, Andreas
---------------------------(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
