Обсуждение: Copy query from a query tab
Hello,
I'm using pgadmin4 4.3 (ran in a docker container) and I'm browsing it using Chromium 56.
If I generate a query in the browser tab (right click > view data > view first 100 rows), then a new tab is opened, named Query-X, with the query (in the red square) at the top and the result table at the bottom:
The query can't be edited and it can't even be copied : ctrl-c is not working and the copy option of the contextual menu (right-click on selection > copy) is disabled .
Is there some rationale to block the edit functionality and the copy functionality or is this a bug ?
Note that edit/copy works fine when creating a query with the top menu option (Tools > "query tool").
Regards,
Cyril
Hi
--
On Mon, Mar 27, 2017 at 11:40 AM, Cyril Jouve <jv.cyril@gmail.com> wrote:
Hello,I'm using pgadmin4 4.3 (ran in a docker container) and I'm browsing it using Chromium 56.If I generate a query in the browser tab (right click > view data > view first 100 rows), then a new tab is opened, named Query-X, with the query (in the red square) at the top and the result table at the bottom:The query can't be edited and it can't even be copied : ctrl-c is not working and the copy option of the contextual menu (right-click on selection > copy) is disabled .Is there some rationale to block the edit functionality and the copy functionality or is this a bug ?Note that edit/copy works fine when creating a query with the top menu option (Tools > "query tool").
Read-only is expected - in View/Edit data mode we cannot allow arbitrary modifications to the SQL query as we have no straightforward way of knowing if a given query will result in data that can be updated.
I would like to change this in the long term (and we intend to), but it's a significant amount of work.
As for the inability copy, that's a bug - please log it at https://redmine.postgresql.org/projects/pgadmin4/issues/new. I took a quick look, but removing the normal classes we use to prevent copying of parts of the UI that really shouldn't be copied didn't help.
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company