From: | benj dev <benj(dot)dev(at)laposte(dot)net> |
---|---|
To: | pgadmin-hackers <pgadmin-hackers(at)postgresql(dot)org> |
Cc: | ashesh(dot)vashi(at)enterprisedb(dot)com, guillaume(at)lelarge(dot)info |
Subject: | Re: New functionality - Table tree view |
Date: | 2014-03-14 16:26:12 |
Message-ID: | 53232DA4.5060608@laposte.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-hackers |
Thanks for reply,
Ok schema can help (I currently use it to "hide" many herited table).
But sometimes I would like to have an overview of my tables, functions
or others objects and if I have to much object it's "difficult" to
apprehend, so my first idea was to arrange that in a tree view.
There is an intermediary level (objects) and it's generate "visual
pollution" and sometimes difficulty to navigate.
With more thinking (thanks to you), maybe a more simple idea will be an
option to put "schemas" a level down (invert object and schema)
To try to better understand me :
Currently we have :
+ Database
+ basename
+ Catalogues
+ Extensions
+ Schemas
+ public
+ Collationnements
+ Functions
+ Tables
+ Types
+ View
+ ...
+ myprivateschema1
+ ...
+ myprivateschema2
+ ...
The idea is an option which allow to obtain :
+ Database
+ basename
+ Catalogues
+ Extensions
+ "NameToInvent"
+ Collationnements
+ public
+ myprivateschema1
+ myprivateschema2
+ Functions
+ public
+ myprivateschema1
+ myprivateschema2
+ Tables
+ public
+ myprivateschema1
+ myprivateschema2
+ Types
+ public
+ myprivateschema1
+ myprivateschema2
+ View
+ public
+ myprivateschema1
+ myprivateschema2
+ ...
Regards
Le 13/03/2014 10:55, Ashesh Vashi a écrit :
> I think - that's where schema helps.
>
>
> On Thu, Mar 13, 2014 at 3:19 PM, <benj(dot)dev(at)laposte(dot)net
> <mailto:benj(dot)dev(at)laposte(dot)net>> wrote:
>
> Hi,
>
> It's been a while I think a possibility of tree view for table will
> be a great improvment for pgadmin.
>
> It's possible to consider "tree view" in differents way
> - Possibility to create virtual directories for tables and
> possibility to expand or not expand these directories
> - Possibilty to group table by a prefix/suffix/regexp of tables names
> - Possibility to group herited tables
> - other possibilities...
>
> When we have hundreds table, it will be a great help. And I think
> with a little imagination we should be able to find a solution
>
> Thanks.
>
>
> --
> Sent via pgadmin-hackers mailing list
> (pgadmin-hackers(at)postgresql(dot)org <mailto:pgadmin-hackers(at)postgresql(dot)org>)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgadmin-hackers
>
>
>
>
> --
> --
>
> Thanks & Regards,
>
> Ashesh Vashi
> EnterpriseDB INDIA: Enterprise PostgreSQL Company
> <http://www.enterprisedb.com>
>
>
>
> /http://www.linkedin.com/in/asheshvashi/
>
From | Date | Subject | |
---|---|---|---|
Next Message | J.F. Oster | 2014-03-19 14:41:39 | Re: PATCH: Enable backwards search in SQL Box |
Previous Message | Dave Page | 2014-03-14 12:40:22 | Re: crypto library is not installed |