Lists: | pgadmin-hackers |
---|
From: | Guillaume Lelarge <guillaume(at)lelarge(dot)info> |
---|---|
To: | pgadmin-hackers(at)postgresql(dot)org |
Cc: | Kevin Macdonald <kevin(dot)macdonald(at)pentura(dot)ca> |
Subject: | Change for connection name |
Date: | 2007-08-02 15:00:21 |
Message-ID: | 46B1F185.80300@lelarge.info |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Lists: | pgadmin-hackers |
Hi all,
I received an interesting request from Kevin Macdonald a few, hum,
months ago. Yes, I'm not really that quick :) But I didn't forget.
He wished to have the username on the query's window title. This is
interesting when you use multiple accounts. Currently, we have :
Query - " + database_name + " on " + host + ":" + port
We wish to have instead :
Query - " + database_name + " on " + user + "@" + host + ":" + port
The patch attached does exactly this. Comments ?
Regards.
--
Guillaume.
<!-- http://abs.traduc.org/
http://lfs.traduc.org/
http://docs.postgresqlfr.org/ -->
Attachment | Content-Type | Size |
---|---|---|
connname.patch | text/x-patch | 512 bytes |
From: | Dave Page <dpage(at)postgresql(dot)org> |
---|---|
To: | Guillaume Lelarge <guillaume(at)lelarge(dot)info> |
Cc: | pgadmin-hackers(at)postgresql(dot)org, Kevin Macdonald <kevin(dot)macdonald(at)pentura(dot)ca> |
Subject: | Re: Change for connection name |
Date: | 2007-08-02 15:31:57 |
Message-ID: | 46B1F8ED.5060502@postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Lists: | pgadmin-hackers |
Guillaume Lelarge wrote:
> Hi all,
>
> I received an interesting request from Kevin Macdonald a few, hum,
> months ago. Yes, I'm not really that quick :) But I didn't forget.
>
> He wished to have the username on the query's window title. This is
> interesting when you use multiple accounts. Currently, we have :
> Query - " + database_name + " on " + host + ":" + port
>
> We wish to have instead :
> Query - " + database_name + " on " + user + "@" + host + ":" + port
>
> The patch attached does exactly this. Comments ?
Could use full URL style syntax perhaps (not sure if it looks too techy
though), eg:
dpage(at)svr(dot)postgresql(dot)org:5432/mydb
/D
From: | Guillaume Lelarge <guillaume(at)lelarge(dot)info> |
---|---|
To: | Dave Page <dpage(at)postgresql(dot)org> |
Cc: | pgadmin-hackers(at)postgresql(dot)org, Kevin Macdonald <kevin(dot)macdonald(at)pentura(dot)ca> |
Subject: | Re: Change for connection name |
Date: | 2007-08-02 15:48:08 |
Message-ID: | 46B1FCB8.6010203@lelarge.info |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Lists: | pgadmin-hackers |
Dave Page a écrit :
> Guillaume Lelarge wrote:
>> I received an interesting request from Kevin Macdonald a few, hum,
>> months ago. Yes, I'm not really that quick :) But I didn't forget.
>>
>> He wished to have the username on the query's window title. This is
>> interesting when you use multiple accounts. Currently, we have :
>> Query - " + database_name + " on " + host + ":" + port
>>
>> We wish to have instead :
>> Query - " + database_name + " on " + user + "@" + host + ":" + port
>>
>> The patch attached does exactly this. Comments ?
>
> Could use full URL style syntax perhaps (not sure if it looks too techy
> though), eg:
>
> dpage(at)svr(dot)postgresql(dot)org:5432/mydb
>
Currently, it is
mydb on svr.postgresql.org:5432
My patch changes this to
mydb on dpage(at)svr(dot)postgresql(dot)org:5432
So dpage(at)svr(dot)postgresql(dot)org:5432/mydb does not seem too techy for me.
Kevin, a comment ?
--
Guillaume.
<!-- http://abs.traduc.org/
http://lfs.traduc.org/
http://docs.postgresqlfr.org/ -->
From: | Guillaume Lelarge <guillaume(at)lelarge(dot)info> |
---|---|
To: | Kevin Macdonald <kevin(dot)macdonald(at)pentura(dot)ca> |
Cc: | Dave Page <dpage(at)postgresql(dot)org>, pgadmin-hackers <pgadmin-hackers(at)postgresql(dot)org> |
Subject: | Re: Change for connection name |
Date: | 2007-08-02 15:56:28 |
Message-ID: | 46B1FEAC.4020203@lelarge.info |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Lists: | pgadmin-hackers |
Kevin Macdonald a écrit :
>> not sure if it looks too techy though
>
> I think so too; it's also a bit wordy. From my experience in an Oracle
> shop, few DBAs are programmer-type people.
>
> However, the choice could be controlled within "File->Options".
>
I don't think a choice is needed here. Moreover, it adds complexity and
this is not what we want on a beta phase.
> A simple alternative to the complexity would simply be
>
> "dpage(at)server_name" -- who you are, and what you connected to.
>
> where "server_name" is what you typed for "name" when you clicked on the
> "wall plug" and established a new server/connection.
>
> I think the low-level details (server URL, port, database) is too much;
> if a person wants these details, they can right-click on a server and
> choose "Properties..."
>
We need the database name "detail" because the server name doesn't imply
it. And using server name is great if you don't change it. I think we
really need every details, URL form or "verbose" form.
--
Guillaume.
<!-- http://abs.traduc.org/
http://lfs.traduc.org/
http://docs.postgresqlfr.org/ -->
From: | Dave Page <dpage(at)postgresql(dot)org> |
---|---|
To: | Guillaume Lelarge <guillaume(at)lelarge(dot)info> |
Cc: | Kevin Macdonald <kevin(dot)macdonald(at)pentura(dot)ca>, pgadmin-hackers <pgadmin-hackers(at)postgresql(dot)org> |
Subject: | Re: Change for connection name |
Date: | 2007-08-02 20:07:08 |
Message-ID: | 46B2396C.2070909@postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Lists: | pgadmin-hackers |
Guillaume Lelarge wrote:
> Kevin Macdonald a écrit :
>>> not sure if it looks too techy though
>> I think so too; it's also a bit wordy. From my experience in an Oracle
>> shop, few DBAs are programmer-type people.
>>
>> However, the choice could be controlled within "File->Options".
>>
>
> I don't think a choice is needed here. Moreover, it adds complexity and
> this is not what we want on a beta phase.
>
>> A simple alternative to the complexity would simply be
>>
>> "dpage(at)server_name" -- who you are, and what you connected to.
>>
>> where "server_name" is what you typed for "name" when you clicked on the
>> "wall plug" and established a new server/connection.
>>
>> I think the low-level details (server URL, port, database) is too much;
>> if a person wants these details, they can right-click on a server and
>> choose "Properties..."
>>
>
> We need the database name "detail" because the server name doesn't imply
> it. And using server name is great if you don't change it. I think we
> really need every details, URL form or "verbose" form.
>
>
Let's just use the form you proposed originally - I'll crawl back in my
hole and stop making silly suggestions :-)
/D
From: | Guillaume Lelarge <guillaume(at)lelarge(dot)info> |
---|---|
To: | Dave Page <dpage(at)postgresql(dot)org> |
Cc: | Kevin Macdonald <kevin(dot)macdonald(at)pentura(dot)ca>, pgadmin-hackers <pgadmin-hackers(at)postgresql(dot)org> |
Subject: | Re: Change for connection name |
Date: | 2007-08-02 21:36:20 |
Message-ID: | 46B24E54.2080205@lelarge.info |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Lists: | pgadmin-hackers |
Dave Page a écrit :
> Guillaume Lelarge wrote:
>> Kevin Macdonald a écrit :
>>>> not sure if it looks too techy though
>>> I think so too; it's also a bit wordy. From my experience in an Oracle
>>> shop, few DBAs are programmer-type people.
>>>
>>> However, the choice could be controlled within "File->Options".
>>>
>> I don't think a choice is needed here. Moreover, it adds complexity and
>> this is not what we want on a beta phase.
>>
>>> A simple alternative to the complexity would simply be
>>>
>>> "dpage(at)server_name" -- who you are, and what you connected to.
>>>
>>> where "server_name" is what you typed for "name" when you clicked on the
>>> "wall plug" and established a new server/connection.
>>>
>>> I think the low-level details (server URL, port, database) is too much;
>>> if a person wants these details, they can right-click on a server and
>>> choose "Properties..."
>>>
>> We need the database name "detail" because the server name doesn't imply
>> it. And using server name is great if you don't change it. I think we
>> really need every details, URL form or "verbose" form.
>>
>>
>
> Let's just use the form you proposed originally - I'll crawl back in my
> hole and stop making silly suggestions :-)
>
Done.
I like having suggestions and ideas :)
--
Guillaume.
<!-- http://abs.traduc.org/
http://lfs.traduc.org/
http://docs.postgresqlfr.org/ -->
From: | "Florian G(dot) Pflug" <fgp(at)phlo(dot)org> |
---|---|
To: | Guillaume Lelarge <guillaume(at)lelarge(dot)info> |
Cc: | Dave Page <dpage(at)postgresql(dot)org>, pgadmin-hackers(at)postgresql(dot)org, Kevin Macdonald <kevin(dot)macdonald(at)pentura(dot)ca> |
Subject: | Re: Change for connection name |
Date: | 2007-08-04 18:27:22 |
Message-ID: | 46B4C50A.7080907@phlo.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Lists: | pgadmin-hackers |
Guillaume Lelarge wrote:
> Dave Page a écrit :
>> Guillaume Lelarge wrote:
>>> I received an interesting request from Kevin Macdonald a few, hum,
>>> months ago. Yes, I'm not really that quick :) But I didn't forget.
>>>
>>> He wished to have the username on the query's window title. This is
>>> interesting when you use multiple accounts. Currently, we have :
>>> Query - " + database_name + " on " + host + ":" + port
>>>
>>> We wish to have instead :
>>> Query - " + database_name + " on " + user + "@" + host + ":" + port
>>>
>>> The patch attached does exactly this. Comments ?
>> Could use full URL style syntax perhaps (not sure if it looks too techy
>> though), eg:
>>
>> dpage(at)svr(dot)postgresql(dot)org:5432/mydb
>>
>
> Currently, it is
> mydb on svr.postgresql.org:5432
>
> My patch changes this to
> mydb on dpage(at)svr(dot)postgresql(dot)org:5432
>
> So dpage(at)svr(dot)postgresql(dot)org:5432/mydb does not seem too techy for me.
Not that it really matters - but I think "db on user(at)host:5432" is half-way
between the full url form, and something more sentence-like, e.g.
"db on host:5432 as user". To me "db on user(at)user:port" opens the question
"why seperate out the db, and stuff the rest into a string".
Having said that, I'll go, shut up, and do real work again :-)
greetings, Florian Pflug
From: | Erwin Brandstetter <brsaweda(at)gmail(dot)com> |
---|---|
To: | pgadmin-hackers(at)postgresql(dot)org |
Cc: | guillaume(at)lelarge(dot)info |
Subject: | Re: Change for connection name |
Date: | 2007-08-10 17:53:48 |
Message-ID: | 1186768428.015609.281900@i38g2000prf.googlegroups.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Lists: | pgadmin-hackers |
On Aug 2, 11:36 pm, guilla(dot)(dot)(dot)(at)lelarge(dot)info (Guillaume Lelarge) wrote:
> Dave Page a crit :
>
(...)
> > Let's just use the form you proposed originally - I'll crawl back in my
> > hole and stop making silly suggestions :-)
>
> Done.
With the more informative connection name (which is a welcome
improvement), we should also increase the width of the database bar in
its docked state (or let the user adjust it). What good is all the
info, if one can't see it? ;)
Something simple like "tester on postgres(at)123(dot)12(dot)123(dot)123:5432" is cut
off in the middle of the IP.
Tested in beta 3 on Win XP.
Regards
Erwin
From: | Dave Page <dpage(at)postgresql(dot)org> |
---|---|
To: | Erwin Brandstetter <brsaweda(at)gmail(dot)com> |
Cc: | pgadmin-hackers(at)postgresql(dot)org, guillaume(at)lelarge(dot)info |
Subject: | Re: Change for connection name |
Date: | 2007-08-13 08:37:07 |
Message-ID: | 46C01833.9040404@postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Lists: | pgadmin-hackers |
Erwin Brandstetter wrote:
> On Aug 2, 11:36 pm, guilla(dot)(dot)(dot)(at)lelarge(dot)info (Guillaume Lelarge) wrote:
>> Dave Page a écrit :
>>
> (...)
>>> Let's just use the form you proposed originally - I'll crawl back in my
>>> hole and stop making silly suggestions :-)
>> Done.
>
> With the more informative connection name (which is a welcome
> improvement), we should also increase the width of the database bar in
> its docked state (or let the user adjust it). What good is all the
> info, if one can't see it? ;)
> Something simple like "tester on postgres(at)123(dot)12(dot)123(dot)123:5432" is cut
> off in the middle of the IP.
> Tested in beta 3 on Win XP.
Tweaked appropriately.
Thanks, Dave.