| From: | Guillaume Lelarge <guillaume(at)lelarge(dot)info> |
|---|---|
| To: | Dave Page <dpage(at)pgadmin(dot)org> |
| Cc: | Thom Brown <thom(at)linux(dot)com>, pgadmin-hackers <pgadmin-hackers(at)postgresql(dot)org> |
| Subject: | Re: [FEATURE] Add schema option to all relevant objects |
| Date: | 2011-07-09 19:49:44 |
| Message-ID: | 1310240985.4434.0.camel@laptop |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgadmin-hackers |
On Sat, 2011-07-09 at 13:39 +0100, Dave Page wrote:
> On Saturday, July 9, 2011, Guillaume Lelarge <guillaume(at)lelarge(dot)info> wrote:
>
> > I would prefer to only refresh the old parent node, and the new parent
> > node. But we have no way to know the new parent node. So I refresh all
> > schemas. Which will bring other performance issues for users with big
> > schemas.
>
> I wonder if we need to think about a way of passing more info down to
> the lower guts of the execution mechanism. We kinda did that already
> when we added the 2 part SQL execution, maybe now we should think
> about a more extensible technique (maybe as simple as passing a simple
> struct of stuff to deal with).
>
Do you have an example? I'm not sure I really understand what you mean.
--
Guillaume
http://blog.guillaume.lelarge.info
http://www.dalibo.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Guillaume Lelarge | 2011-07-09 19:54:20 | pgAdmin III commit: Allow change of schema in the UI |
| Previous Message | pgAdmin Trac | 2011-07-09 19:48:16 | Re: [pgAdmin III] #7: Better display of the logfile in the server status window |