| From: | Dave Page <dpage(at)pgadmin(dot)org> |
|---|---|
| To: | Anil Sahoo <anil(dot)sahoo(at)enterprisedb(dot)com> |
| Cc: | Thom Brown <thom(at)linux(dot)com>, Aditya Toshniwal <aditya(dot)toshniwal(at)enterprisedb(dot)com>, pgadmin-hackers <pgadmin-hackers(at)postgresql(dot)org> |
| Subject: | Re: Regarding feature #6841 |
| Date: | 2024-05-16 09:53:36 |
| Message-ID: | CA+OCxoxqMVUR9JdWSAeZPYxSRpLvZLOED6M3tC1L7GgsnfZ4iQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgadmin-hackers |
On Wed, 15 May 2024 at 12:33, Anil Sahoo <anil(dot)sahoo(at)enterprisedb(dot)com>
wrote:
> Hi Team,
>
> I have implemented the Execute query feature and tested it with different
> kinds of test cases.
>
> FYI the PostgreSQL Do block does not work as a single statement when we
> put the cursor inside the block at different positions.
>
> The cursor position is mentioned using pipe('|') and underlined query is
> the active query that will run on click of Execute query button.
>
> I have attached some screenshots for reference.
>
> Please let me know if you have any questions.
>
That is exactly the sort of behaviour I was afraid of :-(. At least we have
safeguards in place to minimise the chances of the user running something
unexpected.
--
Dave Page
pgAdmin: https://www.pgadmin.org
PostgreSQL: https://www.postgresql.org
EDB: https://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Anthony DeBarros | 2024-05-17 14:01:39 | Testing query execution #6841 |
| Previous Message | Akshay Joshi | 2024-05-16 08:46:30 | Re: pgAgent Job issue: Couldn't get a connection to the database when local SQL mode specified in another database other than postgres |