| From: | Magnus Hagander <magnus(at)hagander(dot)net> |
|---|---|
| To: | Guillaume Lelarge <guillaume(at)lelarge(dot)info> |
| Cc: | pgadmin-hackers(at)postgresql(dot)org |
| Subject: | Re: Schema and tablespace |
| Date: | 2007-12-17 18:00:26 |
| Message-ID: | 4766B93A.4060902@hagander.net |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgadmin-hackers |
Guillaume Lelarge wrote:
> Hi,
>
> One feature I want to add to next pgAdmin release is the change of
> schema for any objects (just as we can change the tablespace or owner of
> an object). I have some ideas on how to do this but I'm wondering if
> there was something that make this impossible to do. (Well, I know,
> strange question, but I don't why we can change tablespace but not
> schema... apart from the treeview changes it applies).
Shouldn't be. The schema is just something at the logical level, so you
should be able to change it around at will.
> Another feature I want deals with tablespace. When I select a
> tablespace, I would like to see all objects that belong to this
> tablespace. The way to handle this would be to add children to the
> tablespace nodes in the treeview. The problem I see is that every new
> object will need at least two nodes on the treeview (one in the schema
> part and one in the tablespace part). Do you see other problems with this ?
It would be neat to have. But maybe that's one step unnecessary - it
might be enough to just have a listview that has a column saying what
type it is, and another one saying the name? And the size probably,
since that's most likely why you're looking there?
//Magnus
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Guillaume Lelarge | 2007-12-17 22:23:50 | Re: Schema and tablespace |
| Previous Message | svn | 2007-12-17 17:01:51 | SVN Commit by guillaume: r6911 - trunk/pgadmin3/pgadmin/dlg |