Skip site navigation (1) Skip section navigation (2)

Re: pgAdmin bug? snapshot

From: "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk>
To: "Andreas Pflug" <pgadmin(at)pse-consulting(dot)de>
Cc: "Michael Shapiro" <mshapiro(at)ncsa(dot)edu>,<pgadmin-support(at)postgresql(dot)org>
Subject: Re: pgAdmin bug? snapshot
Date: 2003-11-20 08:34:22
Message-ID: 03AF4E498C591348A42FC93DEA9661B8720037@mail.vale-housing.co.uk (view raw or flat)
Thread:
Lists: pgadmin-support
 

> -----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.

Regards, Dave.


Responses

pgadmin-support by date

Next:From: Andreas PflugDate: 2003-11-20 09:31:26
Subject: Re: pgAdmin bug? snapshot
Previous:From: Andreas PflugDate: 2003-11-19 22:55:41
Subject: Re: pgAdmin bug? snapshot

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group