From: | Andreas Pflug <pgadmin(at)pse-consulting(dot)de> |
---|---|
To: | Dave Page <dpage(at)vale-housing(dot)co(dot)uk> |
Cc: | pgadmin-hackers(at)postgresql(dot)org |
Subject: | Re: Server discovery |
Date: | 2004-08-03 22:20:25 |
Message-ID: | 41100FA9.2010303@pse-consulting.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-hackers |
Dave Page wrote:
>
>
>
>>-----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.
Frankly, this appears overdesigned to me.
Why not just adding discovered servers at installation time?
Regards,
Andreas
From | Date | Subject | |
---|---|---|---|
Next Message | Dave Page | 2004-08-04 07:05:43 | Re: acinclude.m4 patch |
Previous Message | Dave Page | 2004-08-03 21:04:17 | Re: Server discovery |