From: | Dave Page <dpage(at)pgadmin(dot)org> |
---|---|
To: | "microsys(dot)gr microsys(dot)gr" <microsys(dot)gr(at)gmail(dot)com> |
Cc: | pgAdmin Support <pgadmin-support(at)postgresql(dot)org> |
Subject: | Re: SQL Editor via the View Data context-menu |
Date: | 2017-02-28 10:42:14 |
Message-ID: | CA+OCxoy4YP9KmzTu6+Bh7wcJR7a0+FGa09jR4PWYDCaEqnrWtg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-support |
On Mon, Feb 27, 2017 at 5:31 PM, microsys.gr microsys.gr
<microsys(dot)gr(at)gmail(dot)com> wrote:
> OS Windows 10 64-bit
> Version 1.2
> Python Version 2.7.11
> Flask Version 0.11.1
> Application Mode Desktop
>
> If you open the Query tool via the View Data context-menu,
> the upper panel of the SQL Editor is not working like the editor of the
> Query tool itself (Admin3 worked and could edit select statement text).
> That is a real handicap because have to select /copy text, open a new empty
> Query tool and paste text to SQL Editor.
> It would be perfect if the SQL Editor was operational via View Data also.
This 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 too would like to change this in the long term (and we intend to),
but it's a significant amount of work.
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Harshal Dhumal | 2017-02-28 13:33:37 | Re: pgAdmin 4.1.2 Windows |
Previous Message | microsys.gr microsys.gr | 2017-02-27 17:31:59 | SQL Editor via the View Data context-menu |