From: | "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk> |
---|---|
To: | "Tony Caduto" <tony_caduto(at)amsoftwaredesign(dot)com>, "Kenneth Downs" <ken(at)secdat(dot)com>, <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: GUI Interface |
Date: | 2006-05-12 12:49:13 |
Message-ID: | E7F85A1B5FF8D44C8A1AF6885BC9A0E401388132@ratbert.vale-housing.co.uk |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
> -----Original Message-----
> From: pgsql-general-owner(at)postgresql(dot)org
> [mailto:pgsql-general-owner(at)postgresql(dot)org] On Behalf Of Tony Caduto
> Sent: 12 May 2006 13:40
> To: Kenneth Downs; pgsql-general(at)postgresql(dot)org
> Subject: Re: [GENERAL] GUI Interface
>
> Part of the problem is that pgAdmin III seems to preload
> object properties instead of pulling them in as you need them.
> I have noticed many times in pgAdmin III that when a function
> is edited and saved by someone else on a different
> workstation I can't see those changes until I manually
> refresh the object. When you have a ton of tables etc that
> preloading/caching has to be taking up some time.
It does, for sure. On the other hand though, if you're connected to your
database via a slow network (working from home via modem or VPN for
example), it does mean that every click is instant rather than having to
wait for a query to execute - this is how pgAdmin I used to work, and
frustrated too many people which is why it was changed.
There's an up and downside to each design - just choose the tool that
works in the best way for you at the appropriate price for your wallet.
Regards, Dave
From | Date | Subject | |
---|---|---|---|
Next Message | Kenneth Downs | 2006-05-12 13:02:33 | Re: GUI Interface |
Previous Message | Tony Caduto | 2006-05-12 12:40:08 | Re: GUI Interface |