Re: Server discovery - Mailing list pgadmin-hackers

From Andreas Pflug
Subject Re: Server discovery
Date
Msg-id 41100FA9.2010303@pse-consulting.de
Whole thread Raw
In response to Re: Server discovery  ("Dave Page" <dpage@vale-housing.co.uk>)
List pgadmin-hackers
Dave Page wrote:
>
>
>
>>-----Original Message-----
>>From: Andreas Pflug [mailto:pgadmin@pse-consulting.de]
>>Sent: 03 August 2004 13:05
>>To: Dave Page
>>Cc: pgadmin-hackers@postgresql.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.

Frankly, this appears overdesigned to me.
Why not just adding discovered servers at installation time?

Regards,
Andreas

pgadmin-hackers by date:

Previous
From: cvs@cvs.pgadmin.org
Date:
Subject: CVS Commit by dpage: Added .c_str()'s I missed first time round.
Next
From: cvs@cvs.pgadmin.org
Date:
Subject: CVS Commit by dpage: Store details of discovered local servers in the