Re: Bug report: pgAdmin takes selected portion of query in Query Editor to run

From: Aditya Toshniwal <aditya(dot)toshniwal(at)enterprisedb(dot)com>
To: calle(dot)hedberg(at)gmail(dot)com
Cc: Trung Do <chin(dot)bimbo(at)gmail(dot)com>, richard coleman <rcoleman(dot)ascentgl(at)gmail(dot)com>, "pgadmin-support lists(dot)postgresql(dot)org" <pgadmin-support(at)lists(dot)postgresql(dot)org>
Subject: Re: Bug report: pgAdmin takes selected portion of query in Query Editor to run
Date: 2020-08-13 04:07:32
Message-ID: CAM9w-_kJe3E_TJVq1oeikqAQFhD2htbgv=CnCiKBkp5z-Gca4w@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgadmin-support

Hi Calle,

The feature is not implemented yet -
https://redmine.postgresql.org/issues/3256.

On Thu, Aug 13, 2020 at 4:59 AM Calle Hedberg <calle(dot)hedberg(at)gmail(dot)com>
wrote:

> Hi
>
> I find that a nice feature... But if I may ask a related question that
> baffles me: If I paste multiple queries into a window and then run all of
> them, they all run BUT the output window only show the last sub-query
> result.
>
> Is there a configuration setting that will concatenate output when running
> such sequential queries in one go?
>
> Regards
> Calle
>
> On Wed, 12 Aug 2020 at 22:53, Trung Do <chin(dot)bimbo(at)gmail(dot)com> wrote:
>
>> I see, thanks for the explanation. It's a strange feature then, since
>> I accidentally selected part of the query and was so puzzled at the
>> cryptic error message that followed. And having an error is actually
>> the best case scenario. I can see someone doing copy/paste operations
>> to/from this query editor, somehow have part of the query selected but
>> that part is valid SQL, then run it and have no idea that it's not
>> running the whole thing. Being sneaky around something that deals with
>> data is IMO not a good thing. I think it's better if that's an opt-in
>> behavior instead. Just my 2c.
>>
>>
>> On Wed, 12 Aug 2020 at 15:36, richard coleman
>> <rcoleman(dot)ascentgl(at)gmail(dot)com> wrote:
>> >
>> > That's not a bug, it's a *feature* !!
>> >
>> > Seriously though, presently the query window in pgAdmin4 has two
>> options:
>> > If nothing is selected -> run the entire window
>> > If something is selected -> run just what's selected.
>> >
>> > That's how it's been since, well as long as I can recall. Unlike some
>> other tools, pgAdmin4 lacks the ability to "Run Selected" vs. "Run Entire
>> Query Window", so it implements the previously mentioned logic.
>> >
>> > So I guess what you should probably do is create a *feature* request
>> for this additional functionality.
>> >
>> > rik.
>> >
>> > On Wed, Aug 12, 2020 at 3:18 PM Trung Do <chin(dot)bimbo(at)gmail(dot)com> wrote:
>> >>
>> >> If I enter a well formed SQL query into the Query Editor, but only
>> >> select a portion of the query with the mouse and try to run, pgAdmin
>> >> will try to run the selected portion as the query (and will fail most
>> >> of the time because of syntax error)
>> >>
>> >>
>>
>>
>>
>
> --
>
> *Carl-Anders (Calle) Hedberg*
>
> HISP
>
> Researcher & Technical Specialist
>
> Health Information Systems Programme – South Africa
>
> Cell: +47 41461011 (Norway)
>
> Iridium SatPhone: +8816-315-19119 (usually OFF)
>
> E-mail1: calle(at)hisp(dot)org
>
> E-mail2: calle(dot)hedberg(at)gmail(dot)com
>
> Skype: calle_hedberg
>

--
Thanks,
Aditya Toshniwal
pgAdmin hacker | Sr. Software Engineer | *edbpostgres.com*
<http://edbpostgres.com>
"Don't Complain about Heat, Plant a TREE"

In response to

Responses

Browse pgadmin-support by date

  From Date Subject
Next Message Calle Hedberg 2020-08-13 05:40:28 Re: Bug report: pgAdmin takes selected portion of query in Query Editor to run
Previous Message Calle Hedberg 2020-08-12 23:29:16 Re: Bug report: pgAdmin takes selected portion of query in Query Editor to run