From: | Guillaume Lelarge <guillaume(at)lelarge(dot)info> |
---|---|
To: | Dave Page <dpage(at)postgresql(dot)org> |
Cc: | pgadmin-hackers(at)postgresql(dot)org |
Subject: | Re: Enabling SQL text field in the SQL tab of object dialog |
Date: | 2008-06-17 07:59:19 |
Message-ID: | 48576ED7.5030006@lelarge.info |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-hackers |
Dave Page a écrit :
> On Mon, Jun 16, 2008 at 11:07 PM, Guillaume Lelarge
> <guillaume(at)lelarge(dot)info> wrote:
>> OK, this works on my local branch but I still have one issue with it: if the
>> user change the name of a newly created object in the SQL text field, the
>> treeview will display the name available in the name field, not the real one
>> available in the SQL text field.
>
> The only way I can think to handle that is to refresh the parent
> collection, not just the object being modified.
That's also the way I wanted to handle this. But we get back to the
refresh issue. I will need to fix this one.
> That can be
> potentially dangerous if the user has another property dialogue for a
> sibling object open though (actually that's an issue now iirc - this
> would just make it far more likely to occur).
>
What kind of issue are you talking about? can you give me an example?
--
Guillaume.
http://www.postgresqlfr.org
http://dalibo.com
From | Date | Subject | |
---|---|---|---|
Next Message | Dave Page | 2008-06-17 08:02:07 | Re: Enabling SQL text field in the SQL tab of object dialog |
Previous Message | Dave Page | 2008-06-17 07:45:27 | Re: Enabling SQL text field in the SQL tab of object dialog |