Re: Bug in v1.8.4 - AutoCompletion vs running query

From: "Dave Page" <dpage(at)pgadmin(dot)org>
To: "Horvath Gabor" <dueyduey(at)freemail(dot)hu>
Cc: pgadmin-support(at)postgresql(dot)org
Subject: Re: Bug in v1.8.4 - AutoCompletion vs running query
Date: 2008-08-20 12:42:22
Message-ID: 937d27e10808200542m1b84a17dia488c301f404434b@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgadmin-support

On Fri, Aug 15, 2008 at 4:38 PM, Horvath Gabor <dueyduey(at)freemail(dot)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

In response to

Responses

Browse pgadmin-support by date

  From Date Subject
Next Message Luis Nieto 2008-08-20 13:08:27 Postgresql con DotNetNuke
Previous Message Horvath Gabor 2008-08-15 15:38:33 Bug in v1.8.4 - AutoCompletion vs running query