From: | "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk> |
---|---|
To: | "Andreas Pflug" <pgadmin(at)pse-consulting(dot)de> |
Cc: | <pgadmin-hackers(at)postgresql(dot)org> |
Subject: | Re: Server discovery |
Date: | 2004-08-03 09:29:26 |
Message-ID: | E7F85A1B5FF8D44C8A1AF6885BC9A0E407B3AB@ratbert.vale-housing.co.uk |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-hackers |
-----Original Message-----
From: Andreas Pflug [mailto:pgadmin(at)pse-consulting(dot)de]
Sent: Tue 8/3/2004 11:50 AM
To: Dave Page
Cc: pgadmin-hackers(at)postgresql(dot)org
Subject: Server discovery
> I'm a bit unhappy about the current server discovery feature.
> First of all, on machines without pgsql wx will barf about a missing
> registry key with a message box, quite ugly.
Ack, didn't think of that. Will fix.
> Second, the generated server info can't be edited. Well, currently this
> isn't possible for manual entered servers either without registry
> editing, but we should change that anyway: there's no reason why we
> don't have a dlgServer.cpp except for "it's not done".
Yup, was going to do that tonight. I was intending to add keys as I've done for lastdb and lastschema that can be editted, at least using regedit initially. Such servers will retain their config, but remain 'auto-discovered' at each startup.
> My thought was to push the service information into pgadmin registry
> values when installing, so the settings can be adjusted later.
Yup...
/D
From | Date | Subject | |
---|---|---|---|
Next Message | Andreas Pflug | 2004-08-03 10:50:20 | Server discovery |
Previous Message | cvs | 2004-08-02 22:36:58 | CVS Commit by dpage: Auto-discover locally installed servers when |