Re: [FEATURE] Add schema option to all relevant objects - Mailing list pgadmin-hackers

From Guillaume Lelarge
Subject Re: [FEATURE] Add schema option to all relevant objects
Date
Msg-id 1310240985.4434.0.camel@laptop
Whole thread Raw
In response to Re: [FEATURE] Add schema option to all relevant objects  (Dave Page <dpage@pgadmin.org>)
Responses Re: [FEATURE] Add schema option to all relevant objects  (Dave Page <dpage@pgadmin.org>)
List pgadmin-hackers
On Sat, 2011-07-09 at 13:39 +0100, Dave Page wrote:
> On Saturday, July 9, 2011, Guillaume Lelarge <guillaume@lelarge.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


pgadmin-hackers by date:

Previous
From: "pgAdmin Trac"
Date:
Subject: Re: [pgAdmin III] #7: Better display of the logfile in the server status window
Next
From: Guillaume Lelarge
Date:
Subject: pgAdmin III commit: Allow change of schema in the UI