Re: Bug in v1.8.4 - AutoCompletion vs running query - Mailing list pgadmin-support

From Dave Page
Subject Re: Bug in v1.8.4 - AutoCompletion vs running query
Date
Msg-id 937d27e10808200542m1b84a17dia488c301f404434b@mail.gmail.com
Whole thread Raw
In response to Bug in v1.8.4 - AutoCompletion vs running query  ("Horvath Gabor" <dueyduey@freemail.hu>)
Responses Re: Bug in v1.8.4 - AutoCompletion vs running query  ("Horvath Gabor" <dueyduey@freemail.hu>)
List pgadmin-support
On Fri, Aug 15, 2008 at 4:38 PM, Horvath Gabor <dueyduey@freemail.hu> wrote:
> If I use autocompletion while a query started from the same edit
> window is already running, the whole application freezes until the
> query is finished, and a message appears in the message page reading:
> ********** Error **********
> The query gets committed, its results remain.

There are other potential issues here - for example, error markers can
end up in the wrong place.

For now, I've disabled editing of the text altogether whilst a query
is running. I can't think of any particularly compelling use cases for
allowing that, but I'm open arguments.

-- 
Dave Page
EnterpriseDB UK: http://www.enterprisedb.com


pgadmin-support by date:

Previous
From: "Horvath Gabor"
Date:
Subject: Bug in v1.8.4 - AutoCompletion vs running query
Next
From: Luis Nieto
Date:
Subject: Postgresql con DotNetNuke