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

From Dave Page
Subject Re: [FEATURE] Add schema option to all relevant objects
Date
Msg-id CA+OCxoyXZ5-hQdfK+D69DHqKHoMH-WJDWwaxV66FiyjybWf8+A@mail.gmail.com
Whole thread Raw
In response to Re: [FEATURE] Add schema option to all relevant objects  (Guillaume Lelarge <guillaume@lelarge.info>)
Responses Re: [FEATURE] Add schema option to all relevant objects  (Guillaume Lelarge <guillaume@lelarge.info>)
List pgadmin-hackers
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).

--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake

EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

pgadmin-hackers by date:

Previous
From: Thom Brown
Date:
Subject: Re: Overhaul of type attributes modification
Next
From: Guillaume Lelarge
Date:
Subject: pgAdmin III commit: Fix SQL query for enabled/disabled triggers and rul