From: | "Dave Page" <dpage(at)postgresql(dot)org> |
---|---|
To: | "Guillaume Lelarge" <guillaume(at)lelarge(dot)info> |
Cc: | pgadmin-hackers(at)postgresql(dot)org |
Subject: | Re: Enabling SQL text field in the SQL tab of object dialog |
Date: | 2008-06-17 08:02:07 |
Message-ID: | 937d27e10806170102o6ff6803evc4cd88e6f40eed92@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-hackers |
On Tue, Jun 17, 2008 at 8:59 AM, Guillaume Lelarge
<guillaume(at)lelarge(dot)info> wrote:
>> 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?
When you open a properties dialogue, it gets passed a pointer to the
pgObject which it may use right up until it is closed. If you refresh
part of the tree, you delete and recreate all the pgObjects under the
node you refresh, so the dialogue can end up with a pointer to an
object that's been deleted.
--
Dave Page
EnterpriseDB UK: http://www.enterprisedb.com
From | Date | Subject | |
---|---|---|---|
Next Message | Guillaume Lelarge | 2008-06-17 21:51:30 | Re: Enabling SQL text field in the SQL tab of object dialog |
Previous Message | Guillaume Lelarge | 2008-06-17 07:59:19 | Re: Enabling SQL text field in the SQL tab of object dialog |