| From: | Dave Page <dpage(at)pgadmin(dot)org> |
|---|---|
| To: | Guillaume Lelarge <guillaume(at)lelarge(dot)info> |
| Cc: | Josh Berkus <josh(at)agliodbs(dot)com>, PgAdmin Support <pgadmin-support(at)postgresql(dot)org> |
| Subject: | Re: Minor UI issues for Server Properties dialog box |
| Date: | 2011-01-16 08:32:01 |
| Message-ID: | AANLkTimXg6Y3BOxHGHuJX1S0ECe94m2BBLKdnohhz0=w@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgadmin-support |
On Sat, Jan 15, 2011 at 11:17 PM, Guillaume Lelarge
<guillaume(at)lelarge(dot)info> wrote:
> Le 15/01/2011 23:58, Josh Berkus a écrit :
>> Nothing showstopping, but:
>>
>> 1) After you make changes in the Server Properties dialog, it gives you
>> the fairly useless message that "Some changes will not take effect until
>> the next time pgAdmin connects to the server". The reason this message
>> is useless (and annoying) is that pgAdmin prevents you from changing
>> those fields unless you are disconnected from the server in the first place.
>>
>
> Yeah, I don't like it either. Need to be fixed.
Actually, it is correct; you can tweak the DB Restriction, but it
needs a full refresh to take effect. That said, it is inconsistent
from other settings.
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jeremy Palmer | 2011-01-16 21:50:57 | Re: Calling pgScript from the command line |
| Previous Message | Josh Berkus | 2011-01-16 00:04:59 | Re: Minor UI issues for Server Properties dialog box |