| From: | Dave Page <dpage(at)pgadmin(dot)org> |
|---|---|
| To: | Guillaume Lelarge <guillaume(at)lelarge(dot)info> |
| 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 12:39:29 |
| Message-ID: | CA+OCxoyXZ5-hQdfK+D69DHqKHoMH-WJDWwaxV66FiyjybWf8+A@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgadmin-hackers |
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).
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Guillaume Lelarge | 2011-07-09 12:58:26 | pgAdmin III commit: Fix SQL query for enabled/disabled triggers and rul |
| Previous Message | Thom Brown | 2011-07-09 12:26:55 | Re: Overhaul of type attributes modification |