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

Re: ShowSystemObjects

From: "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk>
To: "Andreas Pflug" <pgadmin(at)pse-consulting(dot)de>,"pgadmin-hackers" <pgadmin-hackers(at)postgresql(dot)org>
Subject: Re: ShowSystemObjects
Date: 2004-06-16 13:33:53
Message-ID: E7F85A1B5FF8D44C8A1AF6885BC9A0E4A9DF@ratbert.vale-housing.co.uk (view raw or flat)
Thread:
Lists: pgadmin-hackers
 

> -----Original Message-----
> From: pgadmin-hackers-owner(at)postgresql(dot)org 
> [mailto:pgadmin-hackers-owner(at)postgresql(dot)org] On Behalf Of 
> Andreas Pflug
> Sent: 16 June 2004 14:07
> To: pgadmin-hackers
> Subject: [pgadmin-hackers] ShowSystemObjects
> 
> I'm just meditating about ShowSystemObjects.
> - Should we retain it as a check menu or move it to options?

My first thought was check menu as I do use it quite often, but then
with everything in schemas now, things don't get quite so cluttered. 6
of one, halfa dozen of the other.... Leave it where it is and save five
minutes of precious time :-)

> - Strictly speaking, reloading the tree isn't necessary. I 
> think we should drop the tree closing code, and leave a note 
> in the docs. We might present a MessageBox to the user 
> reminding him of refreshing the tree if desired, IMHO we can 
> omit that too.

We need to do something, otherwise we risk lot's of support emails along
the lines of 'I switched on system objects, but still didn't see them'.
If the tree can be refreshed cleanly, then let's do that, otherwise,
give the user the option to refresh now of do it himself later
(explaining what'll happen if done now of course).

Regards, Dave.

pgadmin-hackers by date

Next:From: cvsDate: 2004-06-17 18:12:27
Subject: CVS Commit by andreas: copy rows to clipboard from Query Tool and View
Previous:From: Andreas PflugDate: 2004-06-16 13:07:27
Subject: ShowSystemObjects

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