From: | Andreas Pflug <pgadmin(at)pse-consulting(dot)de> |
---|---|
To: | Dave Page <dpage(at)vale-housing(dot)co(dot)uk> |
Cc: | Michael Shapiro <mshapiro(at)ncsa(dot)edu>, pgadmin-support(at)postgresql(dot)org |
Subject: | Re: pgAdmin bug? snapshot |
Date: | 2003-11-20 09:31:26 |
Message-ID: | 3FBC89EE.6000200@pse-consulting.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-support |
Dave Page wrote:
>
>
>
>
>>-----Original Message-----
>>From: Andreas Pflug [mailto:pgadmin(at)pse-consulting(dot)de]
>>Sent: 19 November 2003 22:56
>>To: Dave Page
>>Cc: Michael Shapiro; pgadmin-support(at)postgresql(dot)org
>>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.
>
>
>
It's the environment restauration that triggers this; the database node
will perform the check.
The dependency code evaluates each node independently from the tree, and
will not iterate any client nodes.
Regards,
Andreas
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Shapiro | 2003-11-21 14:29:55 | pg admin bug - view data |
Previous Message | Dave Page | 2003-11-20 08:34:22 | Re: pgAdmin bug? snapshot |