![]() ![]() Less ideal would be to provide some feedback upon clicking the Save button saying that the connection was lost. So ideally, simply clicking on the "Filter Options" button would offer to reconnect you (same as re-executing the query), and once the connection is reestablished, bring up the Filter Options menu. Given that the Save button is disabled in the Filter Options, then clearly pgAdmin knows the connection is lost. This behaviour is shown in the attached screen capture video. The SQL editor in pgAdmin4 doesn't appear have this, is there an alternative that I haven't been able to find, or is there a parameter/command I can add to my script in order to skip errors at runtime In this instance the script is auto-generated and only renames tables/columns which may not exist so the error output is not required. Once you do that, then you can successfully edit the query, as expected. pgAdmin 4 7. ![]() Macros can be used within a query to simplify syntax and allow for dynamic parts. Alternatively, you can query for the specific server version. It turns out that if you subsequently re-execute the old query, then you'll get the message that the database connection was lost and then are offered to reconnect. CTRL/CMD + Return works as a keyboard shortcut to run the query. Now with the direct path to the postgres utility, you can call it with the -V flag as.
0 Comments
Leave a Reply. |