Thread: 1.15 : wxw 2.9.3 : Object browser

1.15 : wxw 2.9.3 : Object browser

From
Colin Beckingham
Date:
Another thought on usability for consideration by the community:

I have one server that contains a number of similar but not identical 
databases that look very much alike in overall appearance, table names etc.

When working with the left panel object browser window to navigate 
between dbs I have a number of times been on the point of making a 
change to the right table but in the wrong database.

This arises since I am working in one db where the structure in the 
object browser is fully open, and I click the + to open another db. 
However this new db tree does not fully open, but there is movement in 
the content of the browser so I am left with the impression that it has, 
so I think I am now in the new db but that is an error.

In order to avoid this issue I have made it a practice to hide all open 
trees before opening a new one.

I wonder if others have experienced this and whether it is worth 
thinking of a one-click hide for all open trees in the tree, say back to 
schema level which is where a db normally opens?
-- 
---
Colin Beckingham
613-454-5369
http://www.it4gh.com



Re: 1.15 : wxw 2.9.3 : Object browser

From
"Strauch, Sheldon"
Date:
The way I've avoided the same issue is to give each of the servers a different background color in the object browser.

On Fri, May 4, 2012 at 9:36 AM, Colin Beckingham <colbec@start.ca> wrote:
Another thought on usability for consideration by the community:

I have one server that contains a number of similar but not identical databases that look very much alike in overall appearance, table names etc.

When working with the left panel object browser window to navigate between dbs I have a number of times been on the point of making a change to the right table but in the wrong database.

This arises since I am working in one db where the structure in the object browser is fully open, and I click the + to open another db. However this new db tree does not fully open, but there is movement in the content of the browser so I am left with the impression that it has, so I think I am now in the new db but that is an error.

In order to avoid this issue I have made it a practice to hide all open trees before opening a new one.

I wonder if others have experienced this and whether it is worth thinking of a one-click hide for all open trees in the tree, say back to schema level which is where a db normally opens?
--
---
Colin Beckingham
613-454-5369
http://www.it4gh.com


--
Sent via pgadmin-support mailing list (pgadmin-support@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgadmin-support



--
Sheldon E. Strauch
Manager, Database Development

Re: 1.15 : wxw 2.9.3 : Object browser

From
Colin Beckingham
Date:
On 05/04/2012 11:52 AM, Strauch, Sheldon wrote:
> The way I've avoided the same issue is to give each of the servers a
> different background color in the object browser.
>
> On Fri, May 4, 2012 at 9:36 AM, Colin Beckingham <colbec@start.ca
> <mailto:colbec@start.ca>> wrote:
>
>     Another thought on usability for consideration by the community:
>
>     I have one server that contains a number of similar but not
>     identical databases that look very much alike in overall appearance,
>     table names etc.
>
>     When working with the left panel object browser window to navigate
>     between dbs I have a number of times been on the point of making a
>     change to the right table but in the wrong database.
>
>     This arises since I am working in one db where the structure in the
>     object browser is fully open, and I click the + to open another db.
>     However this new db tree does not fully open, but there is movement
>     in the content of the browser so I am left with the impression that
>     it has, so I think I am now in the new db but that is an error.
>
>     In order to avoid this issue I have made it a practice to hide all
>     open trees before opening a new one.
>
>     I wonder if others have experienced this and whether it is worth
>     thinking of a one-click hide for all open trees in the tree, say
>     back to schema level which is where a db normally opens?
>

It's an interesting thought, but the colour attribute is attached to the 
server, not the db. All of my dbs are on the same server.

-- 
---
Colin Beckingham
613-454-5369
http://www.it4gh.com


Re: 1.15 : wxw 2.9.3 : Object browser

From
Guillaume Lelarge
Date:
On Fri, 2012-05-04 at 12:33 -0400, Colin Beckingham wrote:
> On 05/04/2012 11:52 AM, Strauch, Sheldon wrote:
> > The way I've avoided the same issue is to give each of the servers a
> > different background color in the object browser.
> >
> > On Fri, May 4, 2012 at 9:36 AM, Colin Beckingham <colbec@start.ca
> > <mailto:colbec@start.ca>> wrote:
> >
> >     Another thought on usability for consideration by the community:
> >
> >     I have one server that contains a number of similar but not
> >     identical databases that look very much alike in overall appearance,
> >     table names etc.
> >
> >     When working with the left panel object browser window to navigate
> >     between dbs I have a number of times been on the point of making a
> >     change to the right table but in the wrong database.
> >
> >     This arises since I am working in one db where the structure in the
> >     object browser is fully open, and I click the + to open another db.
> >     However this new db tree does not fully open, but there is movement
> >     in the content of the browser so I am left with the impression that
> >     it has, so I think I am now in the new db but that is an error.
> >
> >     In order to avoid this issue I have made it a practice to hide all
> >     open trees before opening a new one.
> >
> >     I wonder if others have experienced this and whether it is worth
> >     thinking of a one-click hide for all open trees in the tree, say
> >     back to schema level which is where a db normally opens?
> >
> 
> It's an interesting thought, but the colour attribute is attached to the 
> server, not the db. All of my dbs are on the same server.
> 

And if you have lots of servers, it may get difficult to distinguish
each colour. I've never had such issue, and don't remember another
report like this. Doesn't mean we shouldn't look into it, but not a
priority IMHO.


-- 
Guillaume
http://blog.guillaume.lelarge.info
http://www.dalibo.com