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

I don’t know if it’s even a good idea to change that functionality. When I’m working on performance issues, I very well may put a very complicated SQL statement with several sub-selects in the window, and start with just one of the sub-selects to see what it’s performance issues might be. So it’s not unusual to select a piece of a statement and execute it.

The behavior described by Tung Do is really just a learning step.

> On Aug 12, 2020, at 12:36 PM, 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 <mailto: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)
>
>