Re: Server discovery

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 18:58:07
Message-ID: E7F85A1B5FF8D44C8A1AF6885BC9A0E41A758E@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: 03 August 2004 13:05
> To: Dave Page
> Cc: pgadmin-hackers(at)postgresql(dot)org
> Subject: Re: [pgadmin-hackers] Server discovery
>
> That means additional/different keys?
> If the services is rediscovered every time, how will you
> distinguish them from the same server entered manually?
>
> Autodiscovery on every startup might result in annoyingly
> popping up servers you already changed manually to your
> needs. This seems undesirable.

Absolutely. I already did this for LastDatabase and LastSchema, which
instead of being stored as HKCU\Software\pgAdmin
III\Servers\LastSchemaNN as they are for manually added servers, are
stored as HKCU\Software\pgAdmin III\Servers\LastSchema-XXXX, where XXXX
is the short name of the installed service. That way, as long as the
user doesn't change the name of the service, the changed values will get
re-attached at the next startup.

I'm toying with adding the hostname into the mix as well, just to
prevent possible mixups wth roaming pofiles. Not sure how likely that
scenario is, but I guess it won't hurt.

Regards, Dave.

Responses

Browse pgadmin-hackers by date

  From Date Subject
Next Message cvs 2004-08-03 20:47:48 CVS Commit by dpage: Store details of discovered local servers in the
Previous Message Andreas Pflug 2004-08-03 12:05:01 Re: Server discovery