From: | Dave Page <dpage(at)pgadmin(dot)org> |
---|---|
To: | gabriele(dot)garuglieri(at)infoblu(dot)it |
Cc: | guillaume(at)lelarge(dot)info, bneuhauser(at)real(dot)com, pgadmin-support(at)postgresql(dot)org |
Subject: | Re: Usability improvment ideas |
Date: | 2011-05-11 08:12:33 |
Message-ID: | BANLkTindcH_vcdd_gMEZ2MdTopKPRh6kRQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-support |
On Wed, May 11, 2011 at 8:23 AM, <gabriele(dot)garuglieri(at)infoblu(dot)it> wrote:
>
> Hi all,
> i second the request of Bernhard, especially for the "run current query" or
> better "run current statement block"
>
>>This "view" of a query is too limited.
> There's no need for anything complicated, just put the cursor within a code
> block and execute everything from previuos blank line to next blank line.
> That's incredibly powerful especially when prototyping and the missing of
> this feature is the reason i use pgadmin only for administration and other
> tools like the mentioned squirrel for query building and running.
Hmm, that would certainly involve far less pain than building a parser
to handle "execute current query". We could pretty easily add options
for "execute current line" and "execute current paragraph" (I'd find
those very useful in fact).
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | gabriele.garuglieri | 2011-05-11 09:40:59 | Rif: Re: Usability improvment ideas |
Previous Message | gabriele.garuglieri | 2011-05-11 07:23:30 | Re: Usability improvment ideas |