In the query tool, it would be good if the program links to the latest help
screens for the context-sensitive (F1) help. You are currently pointing to
8.3, whereas I'm running 8.4. It would be best to provide an entry in the
Options dialog, allowing the user to point to a desired location, either a
local install file (my preference), or one at Postgresql. Thus, PGAdmin
would point as desired, regardless of which engine the user chose for that
session.
Appreciatively,
Larry Silvermintz, Ph.D. | Biologist & Engineer
(510) 705-1432 | Invention: image
-----Original Message-----
From: pgadmin-support-owner@postgresql.org
[mailto:pgadmin-support-owner@postgresql.org] On Behalf Of Dave Page
Sent: Sunday, May 10, 2009 4:21 AM
To: Kieran McCusker
Cc: pgadmin-support@postgresql.org; Ashesh Vashi
Subject: Re: [pgadmin-support] Beta 3
On Fri, May 8, 2009 at 10:22 AM, Kieran McCusker
<kieran.mccusker@kwest.info> wrote:
> Could I raise a few small points?
Sure.
> 1. Query window forgets undo history when it loses focus.
> Under Vista if you switch to another window and back to a query window the
> the undo history is forgotten, the find and replace and cut menu items are
> disabled (although still reachable with ctrl-f).
This sounds like it might be related to a copy/paste issue that Ashesh
has sent me a patch for. Ashesh, can you check that please?
> 2. Graphical query builder
> The message boxes "No SQL query was generated" and "The generated SQL
query
> has changed. Do you want to update it?" become rather trying after a while
> (at least to me). Could they not appear as status bar messages?
> The first one would be fine as is, the second raises another slight issue.
> The status bar could say something like "The generated SQL query has
> changed." with undo reverting to the last sql, but what actually happens
is
> that their is a clear window in the history as well, so you need two undos
> to get back to the previous SQL - This is a little confusing could they be
> grouped as a single undo?
If I'm honest, I prefer the positive alert for the second message. I
could be swayed on the first though.
> 3. New Server Registration
> While DB restriction is fixed in server properties, it is not actually
used
> or stored in New Server Registration i.e. entering a DB restriction here
has
> no effect.
Ashesh, can you investigate that as well please?
> 4. The Links in pgAdmin III help do not all work
> I noticed this looking at Connect to Server where at least the
pg_namespace
> link does not work
That's from when the PG docs used to be in the same HTML Help file.
I've changed those links to point to the PostgreSQL website.
Unfortunately I don't see any way to point them to the actual help
source without implementing our own version of the help browser.
> Anyway many thanks again for a great piece of software!
You're welcome.
--
Dave Page
EnterpriseDB UK: http://www.enterprisedb.com
--
Sent via pgadmin-support mailing list (pgadmin-support@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgadmin-support
