Re: pgadmin 4 feature behavior change requests

Hi Alex,

On Wed, Jun 26, 2019 at 10:39 PM Alex Williams <valenceshell(at)protonmail(dot)com>
wrote:

> Hi,
>
> 1. Get rid of the div overlay on query execution.
> There have been many times when I'm running a query and either the
> connection is broken and it takes more than a few minutes for the app to
> detect that and stop, and most times, the Stop button does not work and I
> need to rerun the query again, but have to wait until the div overlay goes
> away...my "trick" is to save the query which sometimes works where the app
> gives the broken connection message, but sometimes it doesn't work -- what
> would be helpful if that there was no div overlay so I can copy/paste the
> query into a new session/tab. Can you just disable the execute query button
> and have status bar somewhere stating the query is running without the
> overlay? It makes for a pretty design, but in real life / workflow wise,
> it's not good.
>
> 2. Have a sql query check button (unless I'm mistaken, I don't see it)
> where it will check if your sql syntax is correct, but wont execute it.
>
> You can create the feature request @
https://redmine.postgresql.org/projects/pgadmin4

> 3. At least on CentOS pgadmin 4.8, if I right click my query to copy it,
> instead of the copy option, I just get panel options. Can we please have
> copy/cut there too?
>
> This one is already logged.

> 4. When right clicking a table and choosing View/Edit data/select top 100
> from it, does the query need to be read only / greyed out? Why not be able
> to do it for convenience and then have the ability to change the query?
>
> pgAdmin 4 has 2 ways for querying the data, one is *Query Tool* where you
can write your own query and view the data and another is *View Data*
through which you can view/filter/modify the data without writing SQL
query. Currently, the implementation of the automatic mode detection of the
Query Tool is in progress, you can get the idea about it from the
pgadmin-hackers group where it is being discussed and the WIP patch is
available.

> Thanks!
>
> Alex
>
>
> Thanks,
Khushboo

>
>
>
>
> Sent with ProtonMail <https://protonmail.com> Secure Email.
>
>