From: | "pgAdmin Trac" <trac(at)code(dot)pgadmin(dot)org> |
---|---|
To: | |
Cc: | pgadmin-hackers(at)postgresql(dot)org |
Subject: | [pgAdmin III] #232: Smart defaults for new connection in query tool |
Date: | 2010-09-07 01:02:30 |
Message-ID: | 045.36ff430fbbd5f83b09a8adf0ea0fa318@code.pgadmin.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-hackers |
#232: Smart defaults for new connection in query tool
-----------------------+----------------------------------------------------
Reporter: brsa | Owner: dpage
Type: feature | Status: new
Priority: minor | Milestone:
Component: pgadmin | Version: trunk
Keywords: querytool | Platform:
-----------------------+----------------------------------------------------
On opening the "Connect to server" dialog, "Database" and "Username"
fields are copied from the current connection. So far so good.
After choosing another "Server", "Database" and "Username" fields default
to the alphabetically first available there. It would be mighty
convenient, however, if the tool could pick identical database and/or user
in case those are present on the new server. Only failing that fall back
to the alphabetically first.
This was part of #209, but got lost in the details.
Also, somewhat related to #211 and maybe #231.
--
Ticket URL: <http://code.pgadmin.org/trac/ticket/232>
pgAdmin III <http://code.pgadmin.org/trac/>
pgAdmin III
From | Date | Subject | |
---|---|---|---|
Next Message | Darth Revan | 2010-09-07 01:08:57 | Re: [pgAdmin III] #232: Smart defaults for new connection in query tool |
Previous Message | pgAdmin Trac | 2010-09-07 00:31:31 | Re: [pgAdmin III] #231: New connection in query tool crashes pgadmin |