Re: [FEATURE] Add schema option to all relevant objects
От | Thom Brown |
---|---|
Тема | Re: [FEATURE] Add schema option to all relevant objects |
Дата | |
Msg-id | CAA-aLv7kiWmnPqW4hk8a6rCaNeB7o7mOWvwbniHOStK1ucxJmA@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: [FEATURE] Add schema option to all relevant objects (Jasmin Dizdarevic <jasmin.dizdarevic@gmail.com>) |
Ответы |
Re: [FEATURE] Add schema option to all relevant objects
|
Список | pgadmin-hackers |
On 5 July 2011 21:14, Jasmin Dizdarevic <jasmin.dizdarevic@gmail.com> wrote: >> > > Did you fix the issue with the refresh of the browser? (I can't check >> > > yet, I'm doing a last time compile of Jasmin's patch :) ) >> > >> > I got it refreshing the node in the original schema, but not the >> > destination one. >> > >> >> Which is an issue. People may understand that pgadmin doesn't know about >> new or altered objects if the object is created or changed outside of >> the UI. But inside the UI, it should refresh its browser. > > He Tom, > can't you use frmMain::GetNodePath and frmMain::SetCurrentNode to do this? > I don't exactly know what you're doing, but it should be possible to replace > old schema name with the new one. > 1. Extract path of old object > 2. replace old schema name with new one > 3. select the object in the new schema > ? I'm not at all familiar with PgAdmin's codebase, I'm just feeling in the dark so I don't know how easy it is to do that. -- Thom Brown Twitter: @darkixion IRC (freenode): dark_ixion Registered Linux user: #516935 EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company
В списке pgadmin-hackers по дате отправления: